To IPv6 - The Dual-stack Adoption Advisory Panel
summary
Kubernetes adds concrete dual‑stack support (introduced in v1.20 and dual-stack graduated v1.23), with core APIs, CNI changes, and an admin network policy proposal so clusters can be dual-stack or IPv6-only out of the box. Implementations let pods carry multiple addresses — currently enforced as pods with two IPs (one v4 + one v6) — enabling end‑to‑end IPv6 testing, IPSec at the network layer, and a migration path; gaps: ULA handling, Nat64 tradeoffs, and cloud tooling/infra like GitHub on IPv6.
AI-written summary · about
chapters (7)
- 0:00Start
- 0:41Introductions
- 7:24Idiosyncrasies to Ipv6
- 21:03Admin Network Policy
- 25:00What Do You See as the Future for Network Components like Load Balancers and Traffic Management in in an Ipv6 or Dual Stack World
- 27:25Do You Guys See any Possibility To Have End-to-End Encrypted Communication between Parts in Kubernetes by Default
- 30:11Call for Action
related talks
32mIPv6 / Dual-Stack in Kubernetes - Why, When, Where and How?
17mThe Long Road to IPv4/IPv6 Dual-stack Kubernetes
06mKeynote: And Here We Go: Dual-stack Networking in Kubernetes
31mDual-stack Kubernetes with Direct server Return
40mOur Experiences Deploying Kubernetes with IPv6
26mIPv6 First, Not Just Ready: Kubernetes Without IPv4 Using Cilium
37mPanel Discussion: Cloud Native Networking State of the Union
19mSIG-network: Updates and Future Directions