Mayday! CNI Overboard!

on YouTube ↗31m

" summary

CNI isn’t Kubernetes-specific and currently provides only add/del plumbing, so teams built a reconcile controller that computes deltas on Pod annotations and adds or removes interfaces to make Multus work — that controller exists and runs. A KEP for native multi-networking splits into use cases, API and implementation; it aims to replace JSON-in-YAML NetworkAttachmentDefinition glue and enable hot‑plug, hardware devices and a garbage collection verb. CNI evolution (see CNI 2.0) must land daemonization, plugin events and device hooks or risk fragmentation.

AI-written summary · about

" chapters (8)

1. 0:00Introduction
2. 0:21CNI challenges today
3. 5:15What CNI really is
4. 9:53Single-interface limits
5. 14:50Kubernetes multi-networking proposal
6. 22:29Multi-networking fixes CNI
7. 27:08CNI 2.0 and multi-networking
8. 30:49Hardware in multi-networking

" related talks

• 46mMulti - Networking Kubernetes Containers with CNIRashid Khan · DevConf.CZ 2019
• 37mIntroduction to CNI, the Container Network Interface ProjectBryan Boreham, Dan Williams · KubeCon + CloudNativeCon North America 2019
• 35mCNI IntroBryan Boreham, Casey Callendrello · KubeCon + CloudNativeCon Europe 2018
• 35mMultiple Networks for Kubernetes WorkloadsDoug Smith, Piotr Skamruk · KubeCon + CloudNativeCon North America 2019
• 37mKubernetes and the CNI: Where We Are and What's Next - Casey Callendrello, CoreOSCasey Callendrello · KubeCon + CloudNativeCon Europe 2018
• 27mTowards CNI v2.0Casey Callendrello · KubeCon + CloudNativeCon Europe 2021
• 31mEverything You Ever Wanted to Know About CNIs (Container Network Interface) and ...Mickael ROGER · Devoxx France 2024
• 34m"My CNI Plugin Did… What?!": Debugging CNI with Style & AplombDaniel Mellado Area, Doug Smith · KubeCon + CloudNativeCon Europe 2022