Which component runs on OpenShift worker nodes to manage containers?

Which component runs on OpenShift worker nodes to manage containers?

• A. API server
• B. Scheduler
• C. Kubelet
• D. Etcd

Answer: (C)

On a worker node, the kubelet is the agent responsible for running and managing containers. It registers the node with the API server, watches for Pod specifications assigned to that node, and uses the container runtime (such as CRI-O or containerd) to start, stop, and monitor containers. The kubelet ensures each pod’s containers are running, healthy, and aligned with the desired state, handling restarts and reporting status back to the control plane. The API server, etcd, and the Scheduler live on the control plane (master nodes) and do not run on worker nodes. The API server exposes the cluster API, etcd stores cluster state, and the Scheduler decides which node should run a given pod. So the component that runs on worker nodes to manage containers is the kubelet.

On a worker node, the kubelet is the agent responsible for running and managing containers. It registers the node with the API server, watches for Pod specifications assigned to that node, and uses the container runtime (such as CRI-O or containerd) to start, stop, and monitor containers. The kubelet ensures each pod’s containers are running, healthy, and aligned with the desired state, handling restarts and reporting status back to the control plane.

The API server, etcd, and the Scheduler live on the control plane (master nodes) and do not run on worker nodes. The API server exposes the cluster API, etcd stores cluster state, and the Scheduler decides which node should run a given pod. So the component that runs on worker nodes to manage containers is the kubelet.