Who's Running My Pods? A Deep Dive into the K8s Container Runtime Interface
summary
Kubernetes relies on a CRI plugin to run containers and this demo maps kubectl -> crictl -> ctr to the live process: a Kubernetes 1.11 cluster on IBM Cloud (Dallas) with containerd 1.1.4 shows an nginx pod, the container appears in crictl and ctr, and the container PID matches the nginx process. containerd runs continuous stress tests (millions of containers weekly) and CRI integration is declared GA, and killing a container triggers kubelet restart of the container.
AI-written summary · about
chapters (5)
- 0:00Kubernetes CRI and runtimes
- 7:15CRI separation from runtimes
- 12:18Runtime choice importance
- 18:45CRI and Containerd demo
- 33:33Q&A
related talks
42mCRI Runtimes Deep Dive: Who's Running My Kubernetes Pod!?
01h 17mIntro + Deep Dive: containerd
37mCRI-O: Under the Hood
34mLet's Try Every CRI Runtime Available for Kubernetes. No, Really!
23mOCI, CRI, ??: Making Sense of the Container Runtime Landscape in Kubernetes - Phil Estes, IBM
33mCRI-O Still Loves Kubernetes
24mOCI, CRI, ??: Making Sense of the Container Runtime Landscape in Kubernetes
34mContainer Runtime Evolving in Kubernetes
