From f7ed70dc9c36a8ede3cb1c0ea9d5fd6dadd8b720 Mon Sep 17 00:00:00 2001 From: lebaudantoine Date: Fri, 25 Oct 2024 13:58:15 +0200 Subject: [PATCH] =?UTF-8?q?=E2=9C=A8(livekit)=20add=20Livekit=20Egress?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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. --- bin/start-kind.sh | 35 +++++++++++++++ src/helm/env.d/dev/values.egress.yaml.gotmpl | 43 +++++++++++++++++++ src/helm/env.d/dev/values.livekit.yaml.gotmpl | 11 ++++- src/helm/helmfile.yaml | 9 ++++ 4 files changed, 96 insertions(+), 2 deletions(-) create mode 100644 src/helm/env.d/dev/values.egress.yaml.gotmpl diff --git a/bin/start-kind.sh b/bin/start-kind.sh index a77f12f6..99595407 100755 --- a/bin/start-kind.sh +++ b/bin/start-kind.sh @@ -97,6 +97,41 @@ data: help: "https://kind.sigs.k8s.io/docs/user/local-registry/" EOF +cat <