Introduction to CRI-O
Talkat KubeCon + CloudNativeCon North America 2019 · on Tuesday, 2019-11-19· at 11:50· Room 33ABC - San Diego Convention Center, Upper Level·
summary
CRI-O implements the Kubernetes CRI with OCI compatibility, calls runtimes like runC and supports Kata and gVisor, uses containers/storage and containers/image, and plugs into CNI for networking. It runs the Kubernetes conformance suite on every PR, versions in lockstep with Kubernetes, and claims you can restart or upgrade the CRI-O binary without killing containers because each container is managed by a conmon monitor (written in C). Security features include SELinux per-pod labels and a default pids 1024 limit.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 0:36What is CRI
- 3:21Why use CRIO
- 5:55CRIO Components
- 7:25Cryo
- 9:22Security
- 11:07Architecture
- 14:20Demo
- 20:05Behind the Scenes
- 23:20What is CRIO
- 24:39Difference between CRIO and Continuity
- 26:33Stability and Scale
- 28:45Copying Files
- 29:31Container Crashes
- 31:14Metrics
- 31:57Podman vs Cryo
- 32:57Upgrade without disruption
- 34:05Config changes
- 35:32Wipeout service
related talks
29mCRI-O: All the Runtime Kubernetes Needs, and Nothing More
31mCRI-O: The Runtime Control Room
46mCRI-O: All the Runtime Kubernetes need
33mCRI-O Still Loves Kubernetes
19mCRI-O development: behind the scenes
23mOCI, CRI, ??: Making Sense of the Container Runtime Landscape in Kubernetes - Phil Estes, IBM
21mCRI-O: Secure, Performant, and Boring...
26mWhat's New in CRI-O?
