Status: IN
Pod placement in OpenShift must satisfy two independent constraint systems simultaneously: the scheduling system (node selectors, taints, affinity rules, topology manager NUMA policies) determines WHERE a pod runs, while the storage lifecycle (CSI provisioning, PVC binding phases, access mode requirements) determines WHETHER the pod's data dependencies can be met at that location.
Both depth-1 nodes represent independent constraint domains that must be jointly satisfied; a pod can match scheduling rules but fail on storage binding, or have storage available but be unschedulable — neither alone determines placement
Depends on (SL): scheduling-constraints-multi-dimensional, storage-lifecycle-from-provisioning-to-reclaim