aloof-scooter-47164
04/30/2026, 2:11 AMtall-airline-16756
04/30/2026, 2:12 AMtall-airline-16756
04/30/2026, 2:12 AMrestartPolicy)?
• Which LiveKit version or deployment method are you using (self-hosted with Helm/docker-compose, or a hosted product)?
With that I can identify whether restartPolicy is unsupported in the proto/schema you’re using and advise a fix or alternative.
Sources: Self-hosted deployments | LiveKit Documentation, with interactive elementsaloof-scooter-47164
04/30/2026, 2:14 AMtall-airline-16756
04/30/2026, 2:14 AMrestartPolicy suddenly became an unknown proto field in your self-hosted setup, I need a couple quick details:
• Which file produced the error (Kubernetes manifest, Helm values, docker-compose, or another config)?
• Paste the 8–12 lines around where restartPolicy appears (or attach the file snippet).
• Which LiveKit version and which deployment method (Helm chart version or docker-compose commit) are you running?
• Any recent changes or upgrades you made before the error started (chart upgrade, Kubernetes version change, editing configs)?
With those I can tell you whether restartPolicy is not allowed in that schema and recommend the exact change to fix it.
, with interactive elementsaloof-scooter-47164
04/30/2026, 2:26 AMtall-airline-16756
04/30/2026, 2:26 AMrestartPolicy entry (or attach the snippet).
• Which LiveKit version and which deployment method (Helm chart version or docker-compose commit) are you running?
• Any recent changes (chart/LiveKit upgrade, edited config, Kubernetes version change)?
Once you share that snippet and the version info I’ll tell you whether restartPolicy is invalid for that schema and the exact change to fix it.
, with interactive elements