Our Experiences Deploying Kubernetes with IPv6
summary
Step-by-step deployment of IPv6 Kubernetes using Cilium CNI, kube-apiserver/controller-manager/scheduler/kubelet and kubeadm patches shows IPv6 is usable now: services use serviceClusterIP fd03::/112 (≈65k services), pod network uses fd00::/80 with per-node /96 subnets (allowing ~65k nodes and ~4.3 billion addresses per node), CoreDNS needs AAAA probe change, kube-proxy can be skipped with Cilium handling service IP→pod routing, nginx ingress serves pod apps after fixing Host header; required a few 1.8+ CLI flags and merged pull requests but the demo works.
AI-written summary · about
chapters (15)
- 0:00Intro
- 0:35What to expect from this talk?
- 4:30Pets vs Cattle again...
- 6:16Let's assemble our cluster
- 8:14Kubernetes cheat sheet
- 11:08kube-scheduler
- 16:11controller-manager
- 20:25docker
- 21:25cni plugin
- 22:57kube-proxy
- 23:19kubelet
- 26:54Where's kube-dns?
- 28:48Where's ingress?
- 32:50Kubernetes cluster - demo!
- 34:13Final thoughts
related talks
26mIPv6 First, Not Just Ready: Kubernetes Without IPv4 Using Cilium
26mSupercharge Kubernetes Networking with Cilium and IPv6
18mThe Road to IPv6 Support in...
32mIPv6 / Dual-Stack in Kubernetes - Why, When, Where and How?
22mNavigating the Kubernetes Networking Maze
33mTo IPv6 - The Dual-stack Adoption Advisory Panel
17mThe Long Road to IPv4/IPv6 Dual-stack Kubernetes
07mWelcome + Opening Remarks