The Easy--Don't Drive Yourself Crazy--Way to Kubernetes Networking
summary
Kubernetes networking works like three stacked networks: physical, pod, and service, and every pod gets a routable IP so pods talk directly. Practical rules: specify pod and service CIDRs when running kubeadm, keep pod and service ranges separate, and expect pod traffic to be encapsulated (tcpdump usually shows it on a virtual iface). kube-proxy uses iptables, nodePort chooses random high ports and can create hotspots, ingress is L7, and stacks discussed include flannel, weave, and calico supports egress rules and BGP scaling; watch leftover CNI files in /etc/cni/net.d.
AI-written summary · about
chapters (18)
- 0:00Intro
- 0:24Accolades
- 1:19Kubernetes Network Topology
- 2:30Useful Network Ranges
- 3:36Key Understanding #1
- 4:19Kubernetes Node
- 5:14Networking Substrate
- 7:24Key Understanding #2
- 8:13Making Setup Easier: CNI
- 9:17CNI Configuration
- 17:33Key Understanding #3
- 17:55Kubernetes Services
- 21:08kube-proxy Randomizer
- 22:34Demonstration
- 26:41Key Understanding #4
- 27:11Kubernetes Ingress
- 29:31Network Stack Choices
- 31:44Summary of Key Understandings
related talks
22mNavigating the Kubernetes Networking Maze
20mKubernetes Networking 101
29mInside Kubernetes Networking
42mKubernetes Networking at Scale
34mUnderstanding the Kubernetes Networking Layer
40mCloud, Kubernetes, and Service Networking - Taming the Turtles
01h 27mKubernetes Networking 101
15mSimplify Kubernetes Connectivity