Modular Overlay Networking Solutions with the Container Network Interface
summary
Recipe and demo for building a working CNI stack: a tiny simple CNI plugin (bash) calls a separate host-local IPAM binary, runtime invokes plugins via STDIN/ENV, and the network is glued by a bridge veth setup that creates a veth pair, moves one end into the container netns, assigns the IP and routes. Uses config files in /etc/cni/net.d and binaries in /opt/cni/bin; demo shows add/delete succeed and JSON results return via stdout.
AI-written summary · about
chapters (8)
- 0:00Start
- 5:03Docker Networking made easy
- 12:46What are the responsibilities of network plugin?
- 13:56Runtime adds/deletes a container
- 14:59Run time invokes CNl network plugin
- 19:43Runtime invokes Nl network plugin
- 23:59CNI Github Repositories
- 28:20Files for demo
related talks
33mKubernetes Networking: How to Write a CNI Plugin From Scratch
32mDemystifying CNI Writing a CNI from Scratch
37mIntroduction to CNI, the Container Network Interface Project
31mEverything You Ever Wanted to Know About CNIs (Container Network Interface) and ...
46mMulti - Networking Kubernetes Containers with CNI
37mKubernetes and the CNI: Where We Are and What's Next - Casey Callendrello, CoreOS
34m"My CNI Plugin Did… What?!": Debugging CNI with Style & Aplomb
39mCloud Native Networking for Containers in AWS using CNI Plugins - Anirudh Aithal
