Let's Try Every CRI Runtime Available for Kubernetes. No, Really!
summary
Live demos spin up Docker, containerd 1.2.6 clusters on GKE and IBM IKS, a cri-o node (OKD), and sandboxed runtimes via containerd shims: Kata (QEMU/KVM or Firecracker backends), Firecracker microVMs, and gVisor via runtime class. Runtime class selects the shim per pod; the v2 shim API removes messy runC replacements. Singularity and Nabla are mentioned but not fully integrated in demos. Containerd’s smaller footprint and wide adoption (included in every Docker install) is emphasized.
AI-written summary · about
chapters (17)
- 0:00Intro
- 0:20Overview
- 1:26Container Runtime Interface
- 1:47Runtime Responsibilities
- 2:25Runtimes Overview
- 3:00Caveats
- 3:37Super Cluster
- 4:03Clusters
- 5:23Docker
- 8:41Container D
- 11:59Creo
- 14:01Creo Uses
- 16:34V2 Shim API
- 25:29firecracker
- 30:06Singularity
- 31:56Nabla
- 32:43Conclusion
related talks
37mLet's Try All the CRI Runtimes: Part 2: Answering the Why Question!
42mCRI Runtimes Deep Dive: Who's Running My Kubernetes Pod!?
24mOCI, CRI, ??: Making Sense of the Container Runtime Landscape in Kubernetes
46mCRI-O: All the Runtime Kubernetes need
35mWhat Container Runtime Do I Need?
39mMore Than Secure: Containerd + KataContainers as Kubernetes Runtime
23mOCI, CRI, ??: Making Sense of the Container Runtime Landscape in Kubernetes - Phil Estes, IBM
34mContainer Runtime Evolving in Kubernetes