OCI, CRI, ??: Making Sense of the Container Runtime Landscape in Kubernetes
summary
OCI defines runtime and image specs (runtime and image spec 1.0 released 2017) and Kubernetes uses the CRI (announced late 2016) so multiple runtimes interoperate: docker, containerd, cri-o, rkt, Singularity, kata, gVisor, Firecracker. containerd is production GA in GKE and IBM managed services and AWS Fargate moves to containerd; OpenShift defaults to cri-o. Kubernetes offers RuntimeClass and crictl to choose and debug runtimes. Choice trades off size, extensibility, and sandbox isolation.
AI-written summary · about
chapters (15)
- 0:00Intro
- 1:15It all began with Docker
- 2:08Container Runtimes
- 3:42The OCI is Born
- 5:33A Common Substrate
- 6:27Ongoing OCI Focus
- 8:16Kubernetes...
- 8:41Kubernetes: Runtime
- 9:47Kubernetes: CRI
- 10:34Who implements the CRI?
- 13:02Current State of Runtimes
- 14:25Why Different Runtimes?
- 17:02Sandboxes
- 18:05Common Interface
- 19:27Summary
related talks
23mOCI, CRI, ??: Making Sense of the Container Runtime Landscape in Kubernetes - Phil Estes, IBM
34mContainer Runtime Evolving in Kubernetes
46mCRI-O: All the Runtime Kubernetes need
42mCRI Runtimes Deep Dive: Who's Running My Kubernetes Pod!?
34mContainer Runtime Evolving in Kubernetes
29mCRI-O: All the Runtime Kubernetes Needs, and Nothing More
34mLet's Try Every CRI Runtime Available for Kubernetes. No, Really!
35mWhat Container Runtime Do I Need?
