Which component is responsible for spawning and running containers in a Kubernetes architecture?

Which component is responsible for spawning and running containers in a Kubernetes architecture?

• A. Low-Level Container Runtime
• B. Kubelet
• C. Kubernetes Scheduler
• D. ETCD

Answer: (A)

Containers on a node are created and run by the container runtime—the low-level engine such as containerd or CRI-O. The Kubelet talks to this runtime via the Container Runtime Interface (CRI) to start, stop, and manage the containers that make up each pod. It’s the runtime that actually launches the container processes; the scheduler only decides where pods should go, and ETCD is just the cluster’s data store. This separation explains why the container runtime is the component responsible for spawning and running containers.

Containers on a node are created and run by the container runtime—the low-level engine such as containerd or CRI-O. The Kubelet talks to this runtime via the Container Runtime Interface (CRI) to start, stop, and manage the containers that make up each pod. It’s the runtime that actually launches the container processes; the scheduler only decides where pods should go, and ETCD is just the cluster’s data store. This separation explains why the container runtime is the component responsible for spawning and running containers.