CNI, CRI, and OCI - Oh My! [I]
summary
Covers three concrete standards and what they actually do: CNI: two calls (ADD/DEL) and plugins that now support IPv6, plugin chaining and port forwarding; widely adopted and nearing 1.0, CRI: an adapter around kubelet implemented over gRPC/protobuf so multiple runtimes plug in (cri-o is a minimal runtime based on runc), OCI: formal image and runtime specs (images are Linux tarballs plus metadata), absorbed appc and reached 1.0 so registries can provide a stable artifact format.
AI-written summary · about
chapters (28)
- 0:00Introduction
- 4:14FracT
- 4:45Whats a Container
- 6:29Why Containers
- 6:54What is CNI
- 7:43CNI vs CNM
- 8:44kubernetes
- 9:10CNI
- 11:30CNI Updates
- 12:38CRI
- 14:36Timeline
- 15:29How to get excited about CRI
- 16:44The real goal of CRI
- 17:20OCI
- 19:15Docker Image Format
- 20:14AppC
- 21:13Container Wars
- 21:41What is the OCI
- 21:52What is a container
- 22:08OCI members
- 23:01OCI image
- 23:26Runtime spec
- 24:07Dandy chart
- 25:04Whats next
- 25:58Wrap up
- 26:12Accessibility optionality
- 26:25Thank you
- 26:43Open Cloud Services
related talks
45mNRI: Extending Containerd And CRI-O With Common Plugins
23mOCI, CRI, ??: Making Sense of the Container Runtime Landscape in Kubernetes - Phil Estes, IBM
38mIntroduction to CRI-O
31mCRI-O: The Runtime Control Room
24mOCI, CRI, ??: Making Sense of the Container Runtime Landscape in Kubernetes
26mWhat's New in CRI-O?
35mCNI Intro
37mIntroduction to CNI, the Container Network Interface Project