CRI-O: All the Runtime Kubernetes Needs, and Nothing More
summary
CRI-O implements Kubernetes’ CRI with a minimal stack: containers/image and containers/storage for images, OCI runtimes like runc and Clear Containers, a lightweight conmon monitor, and a kpod CLI. It passes ~300 CRI, node and end-to-end tests per pull request, ships a 1.0 release, matches CRI-O releases to Kubernetes versions, supports mixed runtimes on one node via pod annotations, and is already targeted for OpenShift integration.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 0:22Why CRIO
- 2:27What makes up a container
- 4:11How to create a root filesystem
- 5:00How to run the container
- 7:10CNI
- 7:39Conmen
- 8:49Pods
- 9:54CRIO Architecture
- 11:34Project Status
- 12:33Demos
- 19:51Next Steps
- 21:29Questions
related talks
46mCRI-O: All the Runtime Kubernetes need
38mIntroduction to CRI-O
31mCRI-O: The Runtime Control Room
33mCRI-O Still Loves Kubernetes
19mCRI-O development: behind the scenes
24mOCI, CRI, ??: Making Sense of the Container Runtime Landscape in Kubernetes
23mOCI, CRI, ??: Making Sense of the Container Runtime Landscape in Kubernetes - Phil Estes, IBM
37mCRI-O: Under the Hood
