Is it k3s viable option for livekit deployment?

Thanks for reaching out, Nouman. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.

Need docs for livekit deployment on hetzner.

Hey there! While LiveKit doesn't have a Hetzner-specific deployment guide, don't worry – the standard VM deployment method with Docker Compose and Caddy works like a charm on Hetzner servers. Deployment steps for Hetzner: 1. First things first, set up a Hetzner server (cloud or dedicated) with a public IP address. 2. Make sure you've got a domain name and can add DNS records for your subdomains. 3. Let's configure your Hetzner firewall – you'll need to open these ports: ◦ 443 (HTTPS and TURN/TLS) ◦ 80 (TLS issuance) ◦ 7881 (WebRTC over TCP) ◦ 3478/UDP (TURN/UDP) ◦ 50000-60000/UDP (WebRTC over UDP) 1. Time to generate your deployment files! Use the LiveKit configuration tool: `docker pull livekit/generate docker run --rm -it -v$PWD:/output livekit/generate`This will create

caddy.yaml

,

docker-compose.yaml

,

livekit.yaml

, and some helpful deployment scripts. 2. Deploy using Docker Compose and Caddy as outlined in the generated files. 3. Pro tip: For automated setup, you can use the generated

cloud-init

file in Hetzner's "User data" field when creating a new cloud instance. If you're planning a production environment, I recommend using compute-optimized instances, 10Gbps ethernet or faster, and host networking to get the best performance. These steps follow the official deployment recommendations and are totally compatible with Hetzner's infrastructure. You've got this! Sources: Deploying LiveKit | LiveKit Docs | Deploying LiveKit | LiveKit Docs | deploy/README.md | Voice Assistants | livekit/livekit_composite | DeepWiki | Deploy to a VM | LiveKit Docs

All this setup is on k3s in hetzner

Hey there! While Hetzner doesn't have specific LiveKit documentation for k3s, don't worry - you can totally deploy LiveKit using the standard Kubernetes process with the official Helm chart. It'll work smoothly on your Hetzner infrastructure! Here's a friendly walkthrough of the key steps: 1. First up, get your k3s cluster set up on Hetzner and make sure each node has a public IP. 2. Let's open those important ports on your Hetzner firewall: ◦ 443 (HTTPS and TURN/TLS) ◦ 80 (TLS issuance) ◦ 7881 (WebRTC over TCP) ◦ 3478/UDP (TURN/UDP) ◦ 50000-60000/UDP (WebRTC over UDP) 1. Install Helm on your management machine - it's super easy! 2. Create a

values.yaml

file using the sample template as your guide. 3. Import your SSL certificates as Kubernetes secrets:

kubectl create secret tls <name> --cert <cert-file> --key <key-file> --namespace <namespace>

4. Time to install LiveKit using Helm with your custom configuration and namespace. 5. Pro tip: Make sure host networking is on for LiveKit pods. Remember, only one LiveKit pod can run per node because of port requirements. 6. Set

terminationGracePeriodSeconds

to 5 hours in your Helm chart for smooth, graceful shutdowns. These steps follow the official deployment recommendations and work great for k3s clusters on Hetzner. No special Hetzner limitations to worry about - just make sure your cluster isn't behind extra NAT layers and all those ports are open and ready to go! Sources: Deploy to Kubernetes | LiveKit Docs | server-sample.yaml | Deploying to production | LiveKit Docs | kubernetes/README.md | Kubernetes & Helm Charts | livekit/livekit_composite | DeepWiki