CRI-O: All the Runtime Kubernetes need
summary
CRI-O is a lightweight Kubernetes-focused container runtime that replaces the Docker daemon by implementing the CRI, tying releases to Kubernetes versions and passes Kubernetes E2E and node tests; it uses OCI runtime and image specs and libraries like containers/image and containers/storage, runs on runc or Clear Containers, and ships a tiny shim called conmon to monitor container lifecycles so kubelet can stop independently. Builds and demos run on minikube/OpenShift, supports mixed runtimes, and reports big memory wins (example: Docker ~1GB vs CRI-O ~100MB).
AI-written summary · about
chapters (10)
- 0:00Introduction to CRI-O
- 1:28History and challenges
- 4:07The CRI standard
- 7:28CRI-O project overview
- 13:49Technical architecture
- 21:27Demo and usage
- 25:26Testing and community
- 30:56Container ecosystem tools
- 36:11Roadmap and conclusion
- 39:23Q&A session
related talks
29mCRI-O: All the Runtime Kubernetes Needs, and Nothing More
38mIntroduction to CRI-O
33mCRI-O Still Loves Kubernetes
31mCRI-O: The Runtime Control Room
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
42mCRI Runtimes Deep Dive: Who's Running My Kubernetes Pod!?
37mCRI-O: Under the Hood
