containerd is a lightweight, portable, CRI-compliant container runtime. Running on each Kubernetes node, it provides the engine that runs application containers. section 1.6
Kubernetes treats the runtime as an external dependency rather than installing it itself. A cluster therefore requires a CRI-compatible runtime, such as containerd, cri-containerd, or CRI-O. section 1.6
Verify containerd operationally with Kubernetes and CRI tooling:
- Run kubectl get no -o wide and read the CONTAINER-RUNTIME column. section 2.1.4
- Inspect a pod with kubectl describe po to find a containerd:// container ID. section 1.6
- Use crictl ps to list containers through the CRI interface. section 2.1.4
Confirm the runtime in kind
kubectl get no -o wide reports containerd://1.7.18 for a kind control-plane node. In a multinode cluster, the same check can show containerd://1.7.24 on both control-plane and worker nodes. section 2.1.4
Figure 1.9 The role of the worker node is to run the application workloads. It also contains kubelet, kube-proxy, and the container runtime (e.g., containerd).
Use the worker-node architecture to place containerd alongside kubelet and kube-proxy, with the node running application workloads. section 1.6


