Hi community,
I am trying to deploy jitsi on Kubernetes cluster but there is an issue
I created the
Config Map
apiVersion: v1
data:
CONFIG: /root/.jitsi-meet-cfg
DOCKER_HOST_ADDRESS: 192.168.50.221
HTTP_PORT: “8000”
HTTPS_PORT: “443”
JICOFO_AUTH_PASSWORD: 48e2d69387deff6d9844656910281608
JICOFO_AUTH_USER: focus
JICOFO_COMPONENT_SECRET: bf142410b2ff9557cbd07762f78f3698
JVB_AUTH_PASSWORD: deeff95a4a0ab5658d6831c7574ba246
JVB_AUTH_USER: jvb
JVB_BREWERY_MUC: jvbbrewery
JVB_PORT: “10000”
JVB_STUN_SERVERS: meet-jit-si-turnrelay.jitsi.net:443
JVB_TCP_HARVESTER_DISABLED: “true”
JVB_TCP_MAPPED_PORT: “4443”
JVB_TCP_PORT: “4443”
PUBLIC_URL: https://mydomain.com
TZ: UTC
XMPP_AUTH_DOMAIN: auth.meet.jitsi
XMPP_BOSH_URL_BASE: http://xmpp.meet.jitsi:5280
XMPP_DOMAIN: meet.jitsi
XMPP_GUEST_DOMAIN: guest.meet.jitsi
XMPP_INTERNAL_MUC_DOMAIN: internal-muc.meet.jitsi
XMPP_MUC_DOMAIN: muc.meet.jitsi
XMPP_SERVER: xmpp.meet.jitsi
kind: ConfigMap
metadata:
creationTimestamp: null
name: cm-env
Prosody service
apiVersion: v1
kind: Service
metadata:
labels:
run: prosody
name: svc2
spec:
ports:
- name: “5222”
port: 5222
targetPort: 5222 - name: “5280”
port: 5280
targetPort: 5280 - name: “5347”
port: 5347
targetPort: 5347
selector:
run: prosody
Prosody pod
apiVersion: v1
kind: Pod
metadata:
labels:
run: prosody
name: prosody
spec:
containers:
- image: jitsi/prosody
name: prosody
ports:- containerPort: 5222
- containerPort: 5347
- containerPort: 5280
env: - name: PUBLIC_URL
valueFrom:
configMapKeyRef:
name: cm-env
key: PUBLIC_URL - name: TZ
valueFrom:
configMapKeyRef:
name: cm-env
key: TZ - name: JICOFO_AUTH_USER
valueFrom:
configMapKeyRef:
name: cm-env
key: JICOFO_AUTH_USER - name: XMPP_AUTH_DOMAIN
valueFrom:
configMapKeyRef:
name: cm-env
key: XMPP_AUTH_DOMAIN - name: XMPP_DOMAIN
valueFrom:
configMapKeyRef:
name: cm-env
key: XMPP_DOMAIN - name: XMPP_GUEST_DOMAIN
valueFrom:
configMapKeyRef:
name: cm-env
key: XMPP_GUEST_DOMAIN - name: XMPP_MUC_DOMAIN
valueFrom:
configMapKeyRef:
name: cm-env
key: XMPP_MUC_DOMAIN - name: JVB_AUTH_PASSWORD
valueFrom:
configMapKeyRef:
name: cm-env
key: JVB_AUTH_PASSWORD - name: JVB_AUTH_USER
valueFrom:
configMapKeyRef:
name: cm-env
key: JVB_AUTH_USER - name: JICOFO_AUTH_PASSWORD
valueFrom:
configMapKeyRef:
name: cm-env
key: JICOFO_AUTH_PASSWORD - name: JICOFO_COMPONENT_SECRET
valueFrom:
configMapKeyRef:
name: cm-env
key: JICOFO_COMPONENT_SECRET - name: XMPP_MUC_DOMAIN
valueFrom:
configMapKeyRef:
name: cm-env
key: XMPP_MUC_DOMAIN - name: XMPP_INTERNAL_MUC_DOMAIN
valueFrom:
configMapKeyRef:
name: cm-env
key: XMPP_INTERNAL_MUC_DOMAIN
Web Pod
apiVersion: v1
kind: Pod
metadata:
labels:
run: web
name: web
spec:
containers:
-
image: jitsi/web
name: web
ports:- containerPort: 80
- containerPort: 43
env: - name: PUBLIC_URL
valueFrom:
configMapKeyRef:
name: cm-env
key: PUBLIC_URL - name: TZ
valueFrom:
configMapKeyRef:
name: cm-env
key: TZ - name: JICOFO_AUTH_USER
valueFrom:
configMapKeyRef:
name: cm-env
key: JICOFO_AUTH_USER - name: XMPP_AUTH_DOMAIN
valueFrom:
configMapKeyRef:
name: cm-env
key: XMPP_AUTH_DOMAIN - name: XMPP_BOSH_URL_BASE
valueFrom:
configMapKeyRef:
name: cm-env
key: XMPP_BOSH_URL_BASE - name: XMPP_DOMAIN
valueFrom:
configMapKeyRef:
name: cm-env
key: XMPP_DOMAIN - name: XMPP_GUEST_DOMAIN
valueFrom:
configMapKeyRef:
name: cm-env
key: XMPP_GUEST_DOMAIN - name: XMPP_MUC_DOMAIN
valueFrom:
configMapKeyRef:
name: cm-env
key: XMPP_MUC_DOMAIN
-
For some reason the web pod fail to resolve the xmpp.meet.jitsi
Error
nginx: [emerg] host not found in upstream “xmpp.meet.jitsi” in /config/nginx/meet.conf:50
When
-
Although when i check the docker-compose implementation i can resolve and ping this domain xmpp.meet.jitsi without any problem from inside the container
-
But in case of kubernetes from inside the container it can’t resolve xmpp.meet.jitsi