CRI Runtimes Deep Dive: Who's Running My Kubernetes Pod!?

on YouTube ↗42m

" summary

Claim: Kubernetes itself contains no code to create or start containers, so since v1.5 the Container Runtime Interface (CRI) lets alternate runtimes plug in. Demo uses a Kubernetes 1.14.1 cluster with containerd 1.2.6 demoed, exercising crictl and ctr to list pods, inspect OCI details, kill a container and show kubelet restarting it. Notes concrete runtimes: containerd, CRI-O, runc, kata, firecracker, gvisor and singularity; runtime class lets nodes offer multiple runtimes.

AI-written summary · about

" chapters (6)

1. 0:00Start
2. 3:07Docker Shim
3. 3:31The Runtime Wars
4. 13:29What Do I Need from a Container Runtime
5. 25:53Deploy Nginx
6. 26:23The Kubernetes Api

" related talks

• 34mLet's Try Every CRI Runtime Available for Kubernetes. No, Really!Phil Estes · KubeCon + CloudNativeCon Europe 2019
• 34mContainer Runtime Evolving in KubernetesPengfei Ni · KubeCon + CloudNativeCon + Open Source Summit China 2019
• 24mOCI, CRI, ??: Making Sense of the Container Runtime Landscape in KubernetesPhil Estes · Kubernetes Forum Seoul 2019
• 35mWho's Running My Pods? A Deep Dive into the K8s Container Runtime InterfacePhil Estes · KubeCon + CloudNativeCon China 2018
• 34mContainer Runtime Evolving in KubernetesPengfei Ni · KubeCon + CloudNativeCon China 2019
• 46mCRI-O: All the Runtime Kubernetes needAntonio Mudarca · QCon São Paulo 2018
• 29mCRI-O: All the Runtime Kubernetes Needs, and Nothing MoreMrunal Patel · KubeCon + CloudNativeCon North America 2017
• 29mWhat's Up With All The Different Container Runtimes? - Ricardo Aravena, Branch MetricsRicardo Aravena · KubeCon + CloudNativeCon Europe 2018