CNI Intro
summary
The CNI project provides a vendor-neutral JSON spec plus runtime and plugin libraries, plus a set of base plugins; five active maintainers and ~90–100 contributors coordinate weekly. The spec exposes two main operations today, add and delete, and is adding get plus result caching so orchestrators (kubelet currently throws away add results) can recover pod IPs; plugin chaining is supported and caching fixes delete/chain corner cases. 0.4 targets get; 1.0 is a freeze for the spec.
AI-written summary · about
chapters (13)
- 0:00Introduction to CNI
- 0:47Understanding the CNI project
- 3:24Project governance
- 4:35Development and roadmap
- 7:03Introducing get and caching
- 10:13Plugin chaining
- 12:34Version 1.0 and future goals
- 14:47Multi-networking discussion
- 17:22IPv6 and dual stack support
- 20:26CNI configuration and demos
- 24:38Dynamic configuration
- 28:33IPAM and debugging
- 29:52Windows support and closing
related talks
37mIntroduction to CNI, the Container Network Interface Project
39mDeep Dive: CNI
31mMayday! CNI Overboard!
28mCNI, CRI, and OCI - Oh My! [I]
33mOverview of CNI 1.0.0 and preview of CNI 2.0
27mTowards CNI v2.0
34m"My CNI Plugin Did… What?!": Debugging CNI with Style & Aplomb
33mKubernetes Networking: How to Write a CNI Plugin From Scratch