~/talk

OCI, CRI, ??: Making Sense of the Container Runtime Landscape in Kubernetes - Phil Estes, IBM

slides:none on file

OCI forms the interoperability layer born in 2015 with the runtime spec and runc implementation (2017), and Kubernetes uses the CRI abstraction so any CRI-compliant runtime can plug in. Major implementations include containerd 18% adoption and cri-o 4% in surveys, containerd is now default in some managed services and Fargate, OpenShift defaults to cri-o, sandboxes like gVisor/Kata/Firecracker are usable via runtimeClass, and operators use crictl talking to the CRI socket for runtime-agnostic ops.

AI-written summary · about

  1. 0:00Intro
  2. 0:27It all began with Docker
  3. 1:35Container Runtimes
  4. 3:04The OCI is Born
  5. 4:40A Common Substrate
  6. 6:09Ongoing OCI Focus
  7. 8:03Kubernetes...
  8. 8:32Kubernetes: Runtime
  9. 9:19Kubernetes: CRI
  10. 10:24Who implements the CRI?
  11. 13:05Current State of Runtimes
  12. 14:42Why Different Runtimes?
  13. 15:44Sandboxes
  14. 16:42Common Interface
  15. 18:00Summary
~/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.