VPC in k8s: Not As Simple As It Looks
summary
Describes adding a private IPAM API to managed Kubernetes to centralize subnet allocation across a region, plus a node agent that writes netplan and binds capsule0 (no DHCP) to attach secondary 192.168.x.x addresses. Also explains a CCM change so load balancers and node status use the private internalIP via a public route to the IPAM; implementation keeps legacy public-IP routing, supports ~ /20 subnets (≈509 hosts), already routes LB traffic to private IPs and defaults to dropping traffic on public interfaces.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 0:57Network needs
- 3:08Private networks theory
- 8:25Private networks in Capsule
- 15:47Cloud Controller Manager integration
- 17:33Current state and future
- 20:32Conclusion
related talks
38mVPCs in Kubernetes
28mIPVS for Scaled Private Cloud Load Balancing [I]
40mCloud, Kubernetes, and Service Networking - Taming the Turtles
42mCo-Evolution of Kubernetes and GCP Networking
51mKubernetes SIG-Network: Intro and Deep-Dive
29mTreating Network Assets as Scheduleable Resources
34mLife of a Packet [I]
20mKubernetes Networking 101