Status: IN
OpenShift pod scheduling operates across multiple constraint dimensions simultaneously: node selectors with six operators (In/NotIn/Exists/DoesNotExist/Gt/Lt), affinity/anti-affinity rules, taint effects (NoSchedule/PreferNoSchedule/NoExecute), scheduling gates (creation-time only), topology manager NUMA policies, and default node selectors that intersect with pod-level selectors — creating a constraint-satisfaction problem, not a simple placement decision.
depth-1 grouping — scheduling is multi-dimensional constraint satisfaction, not simple matching
Depends on (SL): node-selector-operators, node-taint-effects-three, affinity-label-selector-operators, scheduling-gates-set-at-creation-only, scheduler-default-node-selector-intersection, topology-manager-single-numa-strictest