cri-containerd Architecture

3rd chunk of `content/en/blog/_posts/2017-11-00-Containerd-Container-Runtime-Options-Kubernetes.md`

d00a1ce709f767af419aa1a1e45a8ea9969973e30956e82f000000010000027e

  

Compared with the current Docker CRI implementation ([dockershim](https://github.com/kubernetes/kubernetes/tree/master/pkg/kubelet/dockershim)), cri-containerd eliminates an extra hop in the stack, making the stack more stable and efficient.



## Architecture
Cri-containerd uses containerd to manage the full container lifecycle and all container images. As also shown below, cri-containerd manages pod networking via [CNI](https://github.com/containernetworking/cni) (another CNCF project).

Title: cri-containerd Architecture

Summary

Cri-containerd leverages containerd for managing the entire container lifecycle and container images. It also employs Container Network Interface (CNI) for managing pod networking. The architecture diagram illustrates the interaction between Kubelet, cri-containerd (comprising image and runtime services), containerd, and CNI, showcasing how they collectively handle container management and networking within a Kubernetes environment.