IPv6 / Dual-Stack in Kubernetes - Why, When, Where and How?
summary
Kubernetes supports dual-stack GA in Kubernetes 1.23 but it requires worker nodes with both IPv4 and IPv6, control plane CIDR and API server settings for both families, and a dual-stack-capable CNI; services can be single- or dual-stack via spec.ipFamilyPolicy. Cloud load‑balancer support is spotty so NodePort or MetalLB are practical workarounds and MetalLB supports IPv6 on-prem. Adoption is rising — ~40% global IPv6, 63% in Germany — and a Kubermatic dual-stack cluster demo successfully shows pods and services reachable over both protocols.
AI-written summary · about
chapters (8)
- 0:00Introduction and speaker
- 1:11Why IPv6 is needed
- 7:22Dual stack networking explained
- 10:34IPv6 in Kubernetes
- 13:43Enabling dual stack in clusters
- 16:15Cloud provider IPv6 support
- 21:09Dual stack demo
- 25:55Conclusion and Q&A
related talks
33mTo IPv6 - The Dual-stack Adoption Advisory Panel
17mThe Long Road to IPv4/IPv6 Dual-stack Kubernetes
06mKeynote: And Here We Go: Dual-stack Networking in Kubernetes
18mThe Road to IPv6 Support in...
26mIPv6 First, Not Just Ready: Kubernetes Without IPv4 Using Cilium
40mOur Experiences Deploying Kubernetes with IPv6
11mIPv6 in Cloud Foundry - Status Update
31mDual-stack Kubernetes with Direct server Return