In Kubernetes, what event triggers the kube-scheduler to assign a Pod to a specific node?

In Kubernetes, what event triggers the kube-scheduler to assign a Pod to a specific node?

• A. When a Node becomes Ready
• B. When a Pod is deleted
• C. When a new Pod is created and needs to be scheduled
• D. When a Pod finishes initialization

Answer: (C)

Scheduling happens when a Pod that needs a node is created and remains unscheduled (in Pending state with no NodeName). The kube-scheduler watches for such Pods, runs its scheduling algorithm to find a suitable Node that satisfies resource requests and constraints (like taints, tolerations, and affinities), and then binds the Pod to that Node. This binding assigns the Pod to the specific node, after which scheduling moves the Pod toward running. Other events, such as a Node becoming Ready, do not trigger the initial scheduling decision for that Pod.

Scheduling happens when a Pod that needs a node is created and remains unscheduled (in Pending state with no NodeName). The kube-scheduler watches for such Pods, runs its scheduling algorithm to find a suitable Node that satisfies resource requests and constraints (like taints, tolerations, and affinities), and then binds the Pod to that Node. This binding assigns the Pod to the specific node, after which scheduling moves the Pod toward running. Other events, such as a Node becoming Ready, do not trigger the initial scheduling decision for that Pod.