{"id":"autoscaling-and-placement-resource-management","text":"OpenShift workload resource management spans two complementary systems: multi-level autoscaling (ClusterAutoscaler→HPA/KEDA→VPA) adjusts capacity at infrastructure and pod levels, while multi-dimensional scheduling (selectors, taints, affinity, topology, gates) places workloads within that capacity — together forming the complete resource allocation model.","truth_value":"IN","source":"","source_url":"","source_hash":"","justifications":[{"type":"SL","antecedents":["multi-level-autoscaling-architecture","workload-placement-requires-storage-and-scheduling"],"outlist":[],"label":"Autoscaling determines how much capacity exists; scheduling determines where workloads land — combining reveals the full resource management picture."}],"dependents":["autoscaling-placement-within-governance"],"metadata":{},"explanation":{"steps":[{"node":"autoscaling-and-placement-resource-management","truth_value":"IN","reason":"SL justification valid","antecedents":["multi-level-autoscaling-architecture","workload-placement-requires-storage-and-scheduling"],"label":"Autoscaling determines how much capacity exists; scheduling determines where workloads land — combining reveals the full resource management picture."},{"node":"multi-level-autoscaling-architecture","truth_value":"IN","reason":"SL justification valid","antecedents":["keda-custom-metrics-autoscaling-model","autoscaler-requires-machine-autoscaler"],"label":"depth-1 KEDA model covers pod-level scaling; base autoscaler belief covers infrastructure-level; combining reveals a three-tier architecture where each tier scales independently but infrastructure scaling gates the capacity available to pod-level scaling"},{"node":"keda-custom-metrics-autoscaling-model","truth_value":"IN","reason":"SL justification valid","antecedents":["keda-custom-resources","keda-trigger-types","vpa-adjusts-requests-limits"],"label":"KEDA horizontal and VPA vertical autoscaling form a complete scaling model"},{"node":"keda-custom-resources","truth_value":"IN","reason":"premise"},{"node":"keda-trigger-types","truth_value":"IN","reason":"premise"},{"node":"vpa-adjusts-requests-limits","truth_value":"IN","reason":"premise"},{"node":"autoscaler-requires-machine-autoscaler","truth_value":"IN","reason":"premise"},{"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"}]}}