Add support livekit embedded turn server #955
Description
Is your feature request related to a problem? Please describe.
Currently, when deploying Element Call via the ESS Helm charts in environments requiring TURN services for media relay (e.g., behind restrictive firewalls or in certain NAT scenarios), users must provision, configure, and maintain a separate, external TURN server. This adds complexity, operational overhead, and potential points of failure to the deployment.
Describe the solution you'd like
I would like the ESS Helm chart to support and enable the use of the embedded TURN server built into the LiveKit stack. This feature would allow administrators to optionally activate and configure the LiveKit embedded TURN server directly through Helm values, eliminating the need for a separate external TURN service in many deployment scenarios.
Describe alternatives you've considered
The primary alternative is the current method: deploying and managing a separate COTURN or similar TURN server instance. This requires additional Kubernetes manifests, configuration management, monitoring, and maintenance. Another alternative is using a commercial TURN service, which introduces additional cost and external dependency.
Additional context
- The LiveKit stack already includes a production-ready embedded TURN server capability.
- Enabling this would significantly simplify the deployment architecture for Element Call, especially in Proof-of-Concept, development, and smaller-scale production environments.
- Relevant LiveKit documentation on embedded TURN: LiveKit TURN Server
- This feature would make the Helm chart more self-contained and easier to deploy "out of the box" in a wider variety of network environments.