CRI-O Still Loves Kubernetes
summary
CRI-O replaces dockershim as a Kubernetes-only runtime and shows concrete fixes: improved CRI metrics and kubelet communication under load, a new cache-and-throttle flow that avoids repeated name is reserved errors (demo simulates a 4‑minute CNI delay), support for user namespaces 65536 mappings via runtime class annotations, seccomp profile recording using the oci-seccomp-bpf hook (requires CRI-O 1.21), and tooling like cryctl and Podman for debugging and image workflows.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 0:38Overview
- 0:48Latest Features
- 2:30Docker Shim Removal
- 3:33Case Study
- 4:12The Fundamental Problem
- 4:40CRIO Before
- 19:06Username Spaces
- 23:13Second Profiles
- 24:34Cons
- 25:12Demo
- 26:57Cryostatus configuration
- 28:24Cryostatus second profile
- 29:10Multiple annotations
- 30:33Multiple profiles
- 32:27Default profile








