concept CRI in category kubernetes

This is an excerpt from Manning's book Core Kubernetes.
Software engineering and IT is the land of abbreviations. Our latest two are CNI and CRI. Both are API definitions for components that kubelet interfaces with. CNI, Container Network Interface, is a component that provides the networking provisioning for Pods. CRI, Container Runtime Interface, provides the ability to run different types of container runtimes. A cluster is limited to one CNI provider and one container runtime.
By remote, what is meant is that the containerd socket is used as a minimal implementation of an interface that Kubernetes can use to create and manage Pods and their lifecycles. The CRI is a minimal interface that any container runtime can implement; it was mainly designed so that different container runtimes (other than docker) could quickly be innovated on by the community and plugged into and out of Kubernetes.

This is an excerpt from Manning's book Kubernetes in Action.
Kubernetes’ support for other container runtimes doesn’t stop with Docker and rkt. Both of those runtimes were initially integrated directly into Kubernetes, but in Kubernetes version 1.5, the Container Runtime Interface (CRI) was introduced. CRI is a plugin API enabling easy integration of other container runtimes with Kubernetes. People are now free to plug other container runtimes into Kubernetes without having to dig deep into Kubernetes code. All they need to do is implement a few interface methods.
From Kubernetes version 1.6 onward, CRI is the default interface the Kubelet uses. Both Docker and rkt are now used through the CRI (no longer directly).