Cloud, Kubernetes, and Service Networking - Taming the Turtles
summary
Explains how cloud VPCs present a flat Layer‑2‑like space while Kubernetes enforces a separate pod IP space, how CNI plugins (Calico, Cilium, AWS ENI) implement that either by routing, overlays (VXLAN/WireGuard) or attaching real ENIs, and how kube‑proxy writes iptables -> ipset rules so ClusterIP VIPs NAT to backends. Describes service mesh as an Envoy sidecar interception pattern (iptables hooks or CNI init) and notes the controller model (kube‑proxy reconciling endpoints) and why eBPF is being used to replace some iptables churn.
AI-written summary · about
chapters (7)
- 0:00Introduction and VPC context
- 3:49Cloud VPC architecture
- 9:24Kubernetes network model
- 13:37Pod isolation and connectivity
- 19:44CNI plugins and overlays
- 25:35Service load balancing
- 31:45Service meshes and security
related talks
34mUnderstanding the Kubernetes Networking Layer
22mNavigating the Kubernetes Networking Maze
20mKubernetes Networking 101
31mFrom CNI to Service Mesh: Demystifying Kubernetes Networking
32mThe Easy--Don't Drive Yourself Crazy--Way to Kubernetes Networking
25mApplication Networking on Kubernetes, where are we now?
35mNext-level Kubernetes Networking with Cilium - Nico Meisenzahl and Philip Welz
34mLife of a Packet [I]