Multi - Networking Kubernetes Containers with CNI
summary
Explains a working solution that attaches multiple network interfaces to pods using a multus shim that reads CRDs and pod annotations, invokes CNI plugins, and publishes MAC/IP info back into the API; shows the spec, a reference implementation, SR‑IOV device‑plugin integration, and CNI updates for health checks and cached results. Demo fails but implementations exist on GitHub and run in clusters today; ongoing gaps: services/endpoints on secondary nets, network policy, and dynamic attach/detach.
AI-written summary · about
chapters (17)
- 0:00Start
- 1:54What are these things?
- 4:24Kubernetes Networking by Default
- 5:01Things that don't fit the Kubernetes Model
- 8:29NPWG Multi Network Specification vi
- 11:52NPWG Additional Components
- 13:02THE PROBLEM
- 13:15THE SOLUTION
- 13:39WHAT MULTUS DOES
- 14:03Default Network
- 15:09CRDS - Custom Resource Definitions
- 16:30How do I add a configuration for an additional interface?
- 17:23How do I start a pod with an additional interface?
- 17:56What's the result after I've started that pod?
- 20:06Network Plumbing Working Group
- 25:05CNI: V0.4 Specification
- 27:20Multus: Iteration
related talks
35mMultiple Networks for Kubernetes Workloads
31mMayday! CNI Overboard!
33mKubernetes Networking: How to Write a CNI Plugin From Scratch
31mFrom CNI to Service Mesh: Demystifying Kubernetes Networking
31mBreaking the Single-Network Barrier: A Cross-Domain Look at…
31mEverything You Ever Wanted to Know About CNIs (Container Network Interface) and ...
37mIntroduction to CNI, the Container Network Interface Project
40mModular Overlay Networking Solutions with the Container Network Interface