In a Kubernetes cluster, which component runs on every node to manage the lifecycle of containers?

In a Kubernetes cluster, which component runs on every node to manage the lifecycle of containers?

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

Answer: (A)

On every node, the agent that manages the actual container lifecycle is the Kubelet. It watches for Pod specifications from the API server, then uses the node’s container runtime (such as containerd or Docker) to start, stop, and manage containers, ensuring they run in the desired state. The Kubelet also monitors container health, restarts failed containers, and reports status back to the API server so the cluster can respond to changes. This per-node agent is what keeps the node's workload aligned with the overall deployment. Kube-Proxy handles networking rules on the node, the Scheduler assigns Pods to nodes, and Etcd stores cluster state on the control plane.

On every node, the agent that manages the actual container lifecycle is the Kubelet. It watches for Pod specifications from the API server, then uses the node’s container runtime (such as containerd or Docker) to start, stop, and manage containers, ensuring they run in the desired state. The Kubelet also monitors container health, restarts failed containers, and reports status back to the API server so the cluster can respond to changes. This per-node agent is what keeps the node's workload aligned with the overall deployment. Kube-Proxy handles networking rules on the node, the Scheduler assigns Pods to nodes, and Etcd stores cluster state on the control plane.