From 2dd6b99191ab438cf61369e2d8a86e7dc6899540 Mon Sep 17 00:00:00 2001 From: Dmitry Mishin Date: Wed, 15 Apr 2020 03:08:00 -0700 Subject: [PATCH] k8s: specify namespace for secret --- examples/kubernetes/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/examples/kubernetes/README.md b/examples/kubernetes/README.md index 8158dbc..6d5c6e3 100644 --- a/examples/kubernetes/README.md +++ b/examples/kubernetes/README.md @@ -8,13 +8,13 @@ Create a namespace to deploy jitsi to: Add the secret with secret values (replace `...` with some random strings): -`kubectl create secret generic jitsi-config --from-literal=JICOFO_COMPONENT_SECRET=... --from-literal=JICOFO_AUTH_PASSWORD=... --from-literal=JVB_AUTH_PASSWORD=... ` +`kubectl create secret generic jitsi-config -n jitsi --from-literal=JICOFO_COMPONENT_SECRET=... --from-literal=JICOFO_AUTH_PASSWORD=... --from-literal=JVB_AUTH_PASSWORD=... ` Deploy the service to listen for JVB UDP traffic on all cluster nodes port 30300: `kubectl create -f jvb-service.yaml` -Now we can deploy the rest of the application: +Now we can deploy the rest of the application. First modify the `DOCKER_HOST_ADDRESS` env value in deployment.yaml to point to one of nodes in your cluster (or load-balancer for all nodes if you have one), and then deploy it: `kubectl create -f deployment.yaml`