Which component in Kubernetes is responsible to watch newly created Pods with no assigned node, and selects a node for them to run on?

Question

Options

• Aetcd
• Bkube controller-manager
• Ckube proxy
• Dkube scheduler

• B
  3% (1)
• C
  3% (1)
• D
  94% (29)

Explanation

kube-scheduler (D) is specifically designed to watch for unscheduled Pods and make node assignment decisions based on resource availability, affinity rules, taints/tolerations, and other constraints - this is its sole responsibility in the control plane.

etcd (A) is a distributed key-value store that holds all cluster state data; it stores scheduling decisions but never makes them. kube-controller-manager (B) runs control loops that reconcile desired vs. actual state (e.g., managing ReplicaSets, Deployments, and node lifecycle), but scheduling is not one of those loops. kube-proxy (C) runs on every node and handles network rules for Service routing - it operates at the networking layer, not the scheduling layer.

Memory tip: Think of the scheduler as a hotel concierge - when a new guest (Pod) arrives with no room (node) assigned, the concierge evaluates available rooms and assigns the best fit. The name "scheduler" itself signals its job: scheduling workloads onto nodes.

No community discussion yet for this question.