How to Build a Kubernetes Networking Solution from Scratch
summary
A real CNI called Antrea gets built and pushed to production in months by wiring Open vSwitch as the data plane to Kubernetes libraries for the control plane; architecture is one controller plus per-node agents, deployable with a one-line manifest. It implements pod IP allocation, overlay tunnels (Geneve) for cross-node routing, network policy enforcement via a centralized policy computation and runtime visibility through Octant, Prometheus and flow export, and the demo shows it working end to end.
AI-written summary · about
chapters (15)
- 0:00Intro
- 1:26Basics of Container Networking Docker bridge network on Linux
- 5:34Kubernetes Namespace
- 6:20Kubernetes Service
- 8:33Kubernetes Cluster Networking Three communication patterns must be enabled
- 11:08kube-proxy: Service Load Balancing
- 12:22Container Network Interface (CNI) Where does the CNI fit in the Pod's lifecycle?
- 14:13What is Open vSwitch (OVS)? And why use it for Kes networking?
- 16:08Configuring Pod networking with OVS step-by-step
- 16:45Connecting the Pod to the OVS bridge
- 22:41Kes Networking with Open vSwitch Recap
- 27:58Project Antrea Architecture Open vSwitch provides a flexible and performant data plane.
- 34:14Network Policy Implementation
- 40:19The Open vSwitch pipeline
- 44:12Conclusion
related talks
19mThe Easy Button to Kubernetes Networking with Open vSwitch
33mKubernetes Networking: How to Write a CNI Plugin From Scratch
29mInside Kubernetes Networking
20mKubernetes Networking 101
37mKubernetes and the CNI: Where We Are and What's Next - Casey Callendrello, CoreOS
31mFrom CNI to Service Mesh: Demystifying Kubernetes Networking
27mMake Kubernetes Networking Ready for World Class AI and HPC ...
34mHeterogeneous multi-cluster full mesh communication practice