mirror of
https://github.com/suitenumerique/meet.git
synced 2026-08-18 22:36:29 +00:00
lebaudantoine
f7ed70dc9c
Egress is already deployed in staging. But, while working locally on feature relying on Egress, it's not suitable to test your development or iterate. Especially I'll need to test the connection between the Egress and the minio bucket in my next PR. We faced quite a few issue while starting the whole stack. Egress didn't want to start. Its connection with the livekit server while the egress participant was joining the room was not successful. The Turn part of the livekit server helm chart was activated. We needed to update few values to in the helm configuration to enabled this turn. Updated CoreDNS to expose Egress pod. Egress tries connecting to MinIO at 127.0.0.1, where no instance exists. Using minio.127.0.0.1.nip.io resolves to 127.0.0.1, causing Egress to connect to itself for uploads. The CoreDNS rewrite directs this to the Ingress IP, correctly routing to MinIO.
44 lines
932 B
Go Template
44 lines
932 B
Go Template
replicaCount: 1
|
|
terminationGracePeriodSeconds: 18000
|
|
|
|
egress:
|
|
log_level: debug
|
|
ws_url: ws://livekit-livekit-server:80
|
|
insecure: true
|
|
enable_chrome_sandbox: true
|
|
{{- with .Values.livekit.keys }}
|
|
{{- range $key, $value := . }}
|
|
api_key: {{ $key }}
|
|
api_secret: {{ $value }}
|
|
{{- end }}
|
|
{{- end }}
|
|
redis:
|
|
address: redis-master:6379
|
|
password: pass
|
|
s3:
|
|
access_key: meet
|
|
secret: password
|
|
region: local
|
|
bucket: meet-media-storage
|
|
endpoint: http://minio:9000
|
|
force_path_style: true
|
|
|
|
loadBalancer:
|
|
type: nginx
|
|
annotations:
|
|
nginx.ingress.kubernetes.io/rewrite-target: /
|
|
nginx.ingress.kubernetes.io/ssl-redirect: "true"
|
|
cert-manager.io/cluster-issuer: "letsencrypt-prod"
|
|
tls:
|
|
- hosts:
|
|
- livekit-egress.127.0.0.1.nip.io
|
|
secretName: livekit-egress-dinum-cert
|
|
|
|
autoscaling:
|
|
enabled: false
|
|
minReplicas: 1
|
|
maxReplicas: 5
|
|
|
|
nodeSelector: {}
|
|
resources: {}
|