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

Abstract

You’ve probably heard about the OCI—a standardization effort to share a common definition for container runtime, image, and image distribution. Add to that the CRI (container runtime interface) in Kubernetes—designed to abstract the container runtime from the kubelet—and you may start to wonder what all these standards and interfaces mean for you in a Kubernetes world.

As of this year, a long list of runtimes, including CNCF projects containerd and cri-o, all implement the CRI. But did you know there are quite a few others? The unique number of CRI combinations is growing, all of which use the common OCI definitions for runtime and image interoperability.

But how would you decide which container runtime is right for you? Clearly each one has tradeoffs. This talk will help describe the current landscape and give you details on the why and how of each CRI implementation available today.

Date
Location
Sydney, Australia
Avatar
Phil Estes
Distinguished Engineer & CTO, Linux OS and Container Architecture Strategy

Container open source maintainer and technical leader at IBM Cloud.