Which Kubernetes component interacts with the Container Runtime Interface (CRI)?

Which Kubernetes component interacts with the Container Runtime Interface (CRI)?

• A. Kube-Proxy
• B. Kubelet
• C. ETCD
• D. Kube-Scheduler

Answer: (B)

Container Runtime Interface is the bridge that lets Kubernetes manage container lifecycles through the runtime engine on each node. The component that talks to this interface is the kubelet. It runs on every node, watches the pods assigned by the scheduler, and uses the CRI to handle container operations—pulling images, creating the container sandbox, starting and stopping containers, and reporting status back to the control plane. Because of this role, CRI interactions flow through the kubelet. The other components don’t interface with the container runtime. Kube-proxy handles networking rules for services and endpoints. ETCD stores cluster state. Kube-scheduler decides which node runs a pod. They operate at different layers and don’t manage container lifecycles via the CRI.

Container Runtime Interface is the bridge that lets Kubernetes manage container lifecycles through the runtime engine on each node. The component that talks to this interface is the kubelet. It runs on every node, watches the pods assigned by the scheduler, and uses the CRI to handle container operations—pulling images, creating the container sandbox, starting and stopping containers, and reporting status back to the control plane. Because of this role, CRI interactions flow through the kubelet.

The other components don’t interface with the container runtime. Kube-proxy handles networking rules for services and endpoints. ETCD stores cluster state. Kube-scheduler decides which node runs a pod. They operate at different layers and don’t manage container lifecycles via the CRI.