{"id":"workload-placement-requires-storage-and-scheduling","text":"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.","truth_value":"IN","source":"","source_url":"","source_hash":"","justifications":[{"type":"SL","antecedents":["scheduling-constraints-multi-dimensional","storage-lifecycle-from-provisioning-to-reclaim"],"outlist":[],"label":"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"}],"dependents":["autoscaling-and-placement-resource-management"],"metadata":{},"explanation":{"steps":[{"node":"workload-placement-requires-storage-and-scheduling","truth_value":"IN","reason":"SL justification valid","antecedents":["scheduling-constraints-multi-dimensional","storage-lifecycle-from-provisioning-to-reclaim"],"label":"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"},{"node":"scheduling-constraints-multi-dimensional","truth_value":"IN","reason":"SL justification valid","antecedents":["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"],"label":"depth-1 grouping — scheduling is multi-dimensional constraint satisfaction, not simple matching"},{"node":"node-selector-operators","truth_value":"IN","reason":"premise"},{"node":"node-taint-effects-three","truth_value":"IN","reason":"premise"},{"node":"affinity-label-selector-operators","truth_value":"IN","reason":"premise"},{"node":"scheduling-gates-set-at-creation-only","truth_value":"IN","reason":"premise"},{"node":"scheduler-default-node-selector-intersection","truth_value":"IN","reason":"premise"},{"node":"topology-manager-single-numa-strictest","truth_value":"IN","reason":"premise"},{"node":"storage-lifecycle-from-provisioning-to-reclaim","truth_value":"IN","reason":"SL justification valid","antecedents":["ocp-storage-uses-csi-plugin-architecture","pvc-three-phases","unbound-pvc-waits-indefinitely","storageclass-default-reclaimpolicy-delete"],"label":"depth-1 grouping — storage resources follow a complete lifecycle with specific phase transitions and cleanup semantics"},{"node":"ocp-storage-uses-csi-plugin-architecture","truth_value":"IN","reason":"premise"},{"node":"pvc-three-phases","truth_value":"IN","reason":"premise"},{"node":"unbound-pvc-waits-indefinitely","truth_value":"IN","reason":"premise"},{"node":"storageclass-default-reclaimpolicy-delete","truth_value":"IN","reason":"premise"}]}}