Which Kubernetes master component schedules new pods to nodes?
Geena, a cloud architect, uses a master component in the Kubernetes cluster architecture that scans newly generated pods and allocates a node to them. This component can also assign nodes based on factors such as the overall resource requirement, data locality, software/hardware/policy restrictions, and internal workload interventions. Which of the following master components is explained in the above scenario?
Community Votes
100% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The exam tests identifying which Kubernetes control-plane component assigns pods to nodes; the trap is confusing the scheduler with the controller manager or API server, which handle reconciliation and API requests rather than node selection.
This CEH question tests Kubernetes master component responsibilities: Kube-scheduler scans newly created pods and selects a node based on resource needs, locality, and policy constraints. The page confirms why Kube-scheduler, not the API server, etcd, or controller manager, is the component described.
The most common wrong choice is Kube-controller-manager because its name suggests it manages cluster placement; in Kubernetes, controller-manager runs reconciliation loops, while only Kube-scheduler performs the filter-and-score node selection for pending pods.
Community Discussion (4 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Kube-scheduler is the control-plane component that watches for newly created pods with no assigned node and selects a node for them. The scenario's factors—resource requirements, data locality, software/hardware/policy restrictions, and workload interventions—map directly to the scheduler's filtering and scoring phases. Kube-scheduler then records the chosen node binding, making it the master component described by Geena's use case. This is why D is the best fit.Why the Other Options Are Wrong
Kube-apiserver is the REST front end that validates and processes API requests, but it does not pick nodes for pods. Etcd is the consistent key-value store holding cluster state, and it has no scheduling logic. Kube-controller-manager runs control loops such as node, replication, and endpoint controllers; although it can create pods through workload controllers, it does not perform the filter/score algorithm that assigns a node. None of these components matches the allocation decision described.Community Comment Notes
insaniunt describes Kube-scheduler as responsible for deciding which node newly created pods should be scheduled to, considering resource requirements, locality, and constraints. As shaody puts it, Kube-scheduler "scans newly generated pods and allocates a node for them." LordXander links this item to CEHv12 question 3096, reinforcing that the scenario is a direct scheduler-definition question. The learner consensus supports the technical analysis, but the decision here rests on the Kubernetes component responsibilities above.Official Reference
Exam Strategy
Memorize the division of labor in the Kubernetes control plane: apiserver exposes the API, etcd stores state, controller-manager runs reconciliation loops, and kube-scheduler binds pods to nodes. When a question mentions scanning newly generated pods or choosing a node based on resource/locality/policy, map those keywords directly to Kube-scheduler.
Frequently Asked Questions
Why is Kube-controller-manager not the component that assigns pods to nodes?
Kube-controller-manager runs reconciliation controllers for nodes, replicas, endpoints, and similar resources, but node selection for pending pods is performed by Kube-scheduler.
Does kube-apiserver choose a node when a pod is created?
No; kube-apiserver validates and persists the pod request in etcd, then Kube-scheduler watches for unscheduled pods and binds a selected node.