WebRTC: The Kubernetes way
summary
A Kubernetes-native TURN gateway called STUNner uses the Pion library to present a single IP/port ingress, proxying relayed UDP directly to private media-server IPs so the NAT problem disappears and STUNner itself is not the performance bottleneck. Practical deployment notes: implements Kubernetes Gateway API, offers cloud load‑balancer annotations, and needs operator patterns for resilience. Collected about ~200 user questions from GitHub/Discord and finds 30% non-video use cases (remote GPU rendering, cloud gaming, remote browsing); a few users hit cloud LB UDP hashing issues (~3) and plain k8s isn’t always worth the learning curve.
AI-written summary · about
chapters (9)
- 0:00Introduction and background
- 1:36Kubernetes and WebRTC
- 3:56Introducing STUNner
- 6:36User journey and trends
- 8:50Addressing common challenges
- 12:01Market statistics and trends
- 15:02Diverse use cases
- 17:33When not to use Kubernetes
- 21:21Q&A session
related talks
14mMovienight 101: How to Power a Video Streaming with Kubernetes and WebRTC
27mWebRTC does what? Learn how robotics subsecond broadcast and game streaming is powered
37mWebRTC: From The Ground Up
23mPion WebRTC
06mWebRTC and Go
41mServers for WebRTC: It is not all Peer to Peer
27mWebRTC: Real-Time Communications
23mIntroduction to Media Streaming Mesh