Library cluster nodes run containerd as the low-level runtime that kubelet talks to when starting Pod containers. Which interface defines that kubelet-to-runtime contract?
Select an answer to reveal the explanation.
Short Explanation
kubelet does not speak every runtime’s private dialect—it speaks CRI, and containerd (or another runtime) answers. That is the clean socket between “schedule this Pod” and “run these containers.” CNI and CSI plug in elsewhere.
Full Explanation
The Container Runtime Interface (CRI) is the gRPC API kubelet uses to create, start, stop, and remove containers and Pod sandboxes via a runtime such as containerd. CNI handles Pod networking after the sandbox exists; CSI handles volumes. IngressClass is unrelated to the runtime socket.