CRI
Kubernetes 1.5 introduced an internal plugin API named Container Runtime Interface (CRI) to provide easy access to different container runtimes. CRI enables Kubernetes to use a variety of container runtimes without the need to recompile. In theory, Kubernetes could use any container runtime that implements CRI to manage pods, containers and container images.
Source: https://kubernetes.io/blog/2017/11/containerd-container-runtime-options-kubernetes/
Position on the Adoption Curve
Presentations about CRI
CRI Runtimes Deep Dive: Who's Running My Kubernetes Pod!?
Interviews
CRI Runtimes Deep Dive: Who's Running My Kubernetes Pod!?
What do you do at IBM?
I’m a Distinguished Engineer, working as a technical executive for the IBM Watson and Cloud Platform’s CTO office. My key goal as a recently named CTO for container and Linux OS architecture strategy is to connect my years of work in the container open source communities to IBM offerings in our public and private cloud offerings.
What is your talk about?
I am going to start with describing how Kubernetes interfaces to the container runtime layer through an API interface called the Container Runtime Interface (CRI). The CRI allows any container runtime which can implement the API to plug in and provide the container execution layer for Kubernetes pods.
