Building an Interconnected Ecosystem
summary
CNI is a tiny, pragmatic API adopted by Kubernetes, Mesos and Cloud Foundry that exposes three calls: ADD/DEL/GET and composes plugins like Calico, Flannel and Weave. Docker’s libnetwork is rejected for deep dependencies; the community prefers CNI’s low surface area. OCI standardizes runtimes and images (runc is the common runtime) while leaving networking out of scope, so platforms are building runc + CNI adapter glue and planning dynamic network changes on the roadmap.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 0:45Welcome
- 1:40Why do we care
- 4:10Kubernetes projects perspective
- 7:34Richards perspective
- 9:32OCI and CI
- 11:13CI plugin
- 12:07Technology
- 16:00CNCF
- 18:25Kubernetes
- 19:44Community
- 21:23Openended comments
- 23:13Dynamic systems
- 26:29Roadmap
- 27:53Croghan
- 28:33Abby
- 30:08Foundations
- 30:58Conclusion
related talks
22mEmbracing OCI and CNI Open Container Standards Between Garden & Friends
37mOpen Standards - Empowering Cloud-Native Innovation
29mInside Kubernetes Networking
01h 28mIntro + Deep Dive: Kubernetes (Network) SIG
43mContainerization in Mesos, Embracing the Standards
01h 27mKubernetes Networking 101
22mrkt and the Open Container Initiative: Promoting Industry Standards
21mCOSI: The Common Operating System Interface