Hi team! 👋 We're migrating from LiveKit Cloud to self-hosted on AWS EKS (Terramate + OpenTofu, Helm, Karpenter) and would love some guidance before committing to a pattern. A few questions:

1. Helm index looks stale.

Chart.yaml

on

livekit-helm

master is at

livekit-server

1.11.0 /

egress

1.12.0 /

ingress

1.5.0, but

<https://helm.livekit.io>

only serves 1.9.0 / 1.8.4 / 1.2.2 (egress last published May 2024). Is a re-publish coming, or should we consume the chart from a git ref?

2. Recommended EKS pattern?

hostNetwork: true

+ dedicated node group, or STUNner /

l7mp/livekit-operator

in front? Any sharp edges with Karpenter consolidation or NLB UDP for TURN?

3. Backend: has anyone validated distributed mode against ElastiCache Valkey (Redis-protocol fork), or should we use real Redis?

4. Egress to S3 via EKS Pod Identity / IRSA — any gotchas vs. static creds?

Thanks!

Using hostnetwork with a public dedicated node group will keep the architecture simple. Valkey works well.