During the Filtering stage of the Kube-Scheduler's process, what happens?

During the Filtering stage of the Kube-Scheduler's process, what happens?

• A. It finds nodes that meet the scheduling requirements
• B. It binds the Pod to a selected node
• C. It calculates node resource usage
• D. It updates the cluster state

Answer: (A)

During Filtering, the scheduler quickly screens potential nodes to see which ones can actually host the pod. It checks each node against the pod’s constraints—enough CPU, memory, and other requested resources; tolerations for taints; node selectors and node affinity requirements; and any additional rules like pod affinity/anti-affinity or topology constraints. Nodes that don’t meet these requirements are excluded, leaving a smaller set of feasible nodes to consider. This narrowed pool is then passed to the next phase, where the remaining nodes are scored to pick the best fit and eventually bound to a specific node.

During Filtering, the scheduler quickly screens potential nodes to see which ones can actually host the pod. It checks each node against the pod’s constraints—enough CPU, memory, and other requested resources; tolerations for taints; node selectors and node affinity requirements; and any additional rules like pod affinity/anti-affinity or topology constraints. Nodes that don’t meet these requirements are excluded, leaving a smaller set of feasible nodes to consider. This narrowed pool is then passed to the next phase, where the remaining nodes are scored to pick the best fit and eventually bound to a specific node.