~/talk

OCI, CRI, ??: Making Sense of the Container Runtime Landscape in Kubernetes

Talkat Kubernetes Forum Seoul 2019 · on Monday, 2019-12-09· at 16:15· Baekdu 1+2· [kubernetes, security]
slides:none on file

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

  1. 0:00Intro
  2. 1:15It all began with Docker
  3. 2:08Container Runtimes
  4. 3:42The OCI is Born
  5. 5:33A Common Substrate
  6. 6:27Ongoing OCI Focus
  7. 8:16Kubernetes...
  8. 8:41Kubernetes: Runtime
  9. 9:47Kubernetes: CRI
  10. 10:34Who implements the CRI?
  11. 13:02Current State of Runtimes
  12. 14:25Why Different Runtimes?
  13. 17:02Sandboxes
  14. 18:05Common Interface
  15. 19:27Summary
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.