Which control plane component is responsible for scheduling pods to nodes?

Which control plane component is responsible for scheduling pods to nodes?

• A. Controller Manager
• B. Scheduler
• C. API server
• D. Etcd

Answer: (B)

Pod placement is determined by the scheduling component of the Kubernetes control plane. It monitors for pods that don’t yet have a node and evaluates which nodes can run them based on each pod’s resource requests, constraints like node selectors, affinity/anti-affinity rules, and taints/tolerations, as well as current node capacity. After comparing candidates, it binds the pod to the most suitable node, finalizing the scheduling so the pod starts running there. This role is separate from other control plane components: the API server handles requests and cluster state, etcd is the backing data store, and the controller manager runs controllers that reconcile desired and actual state. So the scheduler is the component responsible for deciding where pods run.

Pod placement is determined by the scheduling component of the Kubernetes control plane. It monitors for pods that don’t yet have a node and evaluates which nodes can run them based on each pod’s resource requests, constraints like node selectors, affinity/anti-affinity rules, and taints/tolerations, as well as current node capacity. After comparing candidates, it binds the pod to the most suitable node, finalizing the scheduling so the pod starts running there. This role is separate from other control plane components: the API server handles requests and cluster state, etcd is the backing data store, and the controller manager runs controllers that reconcile desired and actual state. So the scheduler is the component responsible for deciding where pods run.