{"id":"progressive-update-across-heterogeneous-fleet","text":"OpenShift progressive update strategies (canary MCPs, EUS-to-EUS skips) must navigate the heterogeneous node fleet: RHCOS nodes accept updates via rpm-ostree atomic images while Windows nodes diverge entirely, and install-time locks (FIPS, network plugin) create irreversible boundaries that updates cannot cross.","truth_value":"IN","source":"","source_url":"","source_hash":"","justifications":[{"type":"SL","antecedents":["progressive-update-within-lifecycle-bounds","lifecycle-constrained-across-heterogeneous-fleet"],"outlist":[],"label":"Update strategies assume orderly rollout but the fleet is fundamentally heterogeneous — combining reveals the tension between progressive updates and fleet diversity."}],"dependents":["security-constrains-entire-update-path"],"metadata":{},"explanation":{"steps":[{"node":"progressive-update-across-heterogeneous-fleet","truth_value":"IN","reason":"SL justification valid","antecedents":["progressive-update-within-lifecycle-bounds","lifecycle-constrained-across-heterogeneous-fleet"],"label":"Update strategies assume orderly rollout but the fleet is fundamentally heterogeneous — combining reveals the tension between progressive updates and fleet diversity."},{"node":"progressive-update-within-lifecycle-bounds","truth_value":"IN","reason":"SL justification valid","antecedents":["platform-lifecycle-bounded-at-install-and-update","update-strategy-canary-and-control-plane-model"],"label":"depth-2 lifecycle boundaries define what is mutable; depth-1 update strategies define how mutations are applied — combining shows that update risk mitigation is bounded by irreversible install-time choices"},{"node":"platform-lifecycle-bounded-at-install-and-update","truth_value":"IN","reason":"SL justification valid","antecedents":["install-time-irreversible-constraints","version-coupling-and-update-governance"],"label":"depth-2 — lifecycle rigidity at both install and update boundaries constrains all platform evolution"},{"node":"install-time-irreversible-constraints","truth_value":"IN","reason":"SL justification valid","antecedents":["ocp-security-fips-install-time-only","cpu-partitioning-install-time-only","network-plugin-selected-at-install-time"],"label":"Three independent install-time-only constraints form a coherent class of irreversible cluster decisions"},{"node":"ocp-security-fips-install-time-only","truth_value":"IN","reason":"premise"},{"node":"cpu-partitioning-install-time-only","truth_value":"IN","reason":"premise"},{"node":"network-plugin-selected-at-install-time","truth_value":"IN","reason":"premise"},{"node":"version-coupling-and-update-governance","truth_value":"IN","reason":"SL justification valid","antecedents":["cnv-version-must-match-ocp-version","cnv-update-ocp-first-then-cnv","hcp-update-order-management-mce-hosted","ocp-rollback-not-supported"],"label":"Version coupling rules and forward-only updates form a strict upgrade governance model"},{"node":"cnv-version-must-match-ocp-version","truth_value":"IN","reason":"premise"},{"node":"cnv-update-ocp-first-then-cnv","truth_value":"IN","reason":"premise"},{"node":"hcp-update-order-management-mce-hosted","truth_value":"IN","reason":"premise"},{"node":"ocp-rollback-not-supported","truth_value":"IN","reason":"premise"},{"node":"update-strategy-canary-and-control-plane-model","truth_value":"IN","reason":"SL justification valid","antecedents":["ocp-canary-updates-custom-machineconfigpools","ocp-control-plane-only-update-even-minor-versions"],"label":"Two base beliefs about update strategies combine into a dual-scope risk mitigation model"},{"node":"ocp-canary-updates-custom-machineconfigpools","truth_value":"IN","reason":"premise"},{"node":"ocp-control-plane-only-update-even-minor-versions","truth_value":"IN","reason":"premise"},{"node":"lifecycle-constrained-across-heterogeneous-fleet","truth_value":"IN","reason":"SL justification valid","antecedents":["platform-lifecycle-bounded-at-install-and-update","node-fleet-heterogeneous-runtime-model"],"label":"depth-2 lifecycle boundaries + depth-2 heterogeneous node model combine into a constrained lifecycle management problem"},{"node":"platform-lifecycle-bounded-at-install-and-update","truth_value":"IN","reason":"SL justification valid","antecedents":["install-time-irreversible-constraints","version-coupling-and-update-governance"],"label":"depth-2 — lifecycle rigidity at both install and update boundaries constrains all platform evolution"},{"node":"install-time-irreversible-constraints","truth_value":"IN","reason":"SL justification valid","antecedents":["ocp-security-fips-install-time-only","cpu-partitioning-install-time-only","network-plugin-selected-at-install-time"],"label":"Three independent install-time-only constraints form a coherent class of irreversible cluster decisions"},{"node":"ocp-security-fips-install-time-only","truth_value":"IN","reason":"premise"},{"node":"cpu-partitioning-install-time-only","truth_value":"IN","reason":"premise"},{"node":"network-plugin-selected-at-install-time","truth_value":"IN","reason":"premise"},{"node":"version-coupling-and-update-governance","truth_value":"IN","reason":"SL justification valid","antecedents":["cnv-version-must-match-ocp-version","cnv-update-ocp-first-then-cnv","hcp-update-order-management-mce-hosted","ocp-rollback-not-supported"],"label":"Version coupling rules and forward-only updates form a strict upgrade governance model"},{"node":"cnv-version-must-match-ocp-version","truth_value":"IN","reason":"premise"},{"node":"cnv-update-ocp-first-then-cnv","truth_value":"IN","reason":"premise"},{"node":"hcp-update-order-management-mce-hosted","truth_value":"IN","reason":"premise"},{"node":"ocp-rollback-not-supported","truth_value":"IN","reason":"premise"},{"node":"node-fleet-heterogeneous-runtime-model","truth_value":"IN","reason":"SL justification valid","antecedents":["rhcos-immutable-update-model","windows-node-architectural-divergence"],"label":"depth-2 — RHCOS and Windows nodes have incompatible runtime models coexisting in one cluster"},{"node":"rhcos-immutable-update-model","truth_value":"IN","reason":"SL justification valid","antecedents":["rhcos-nodes-immutable","rhcos-rpm-ostree-updates","image-layering-verify-rpm-ostree-status"],"label":"Three facets of the same immutable-OS operational model"},{"node":"rhcos-nodes-immutable","truth_value":"IN","reason":"premise"},{"node":"rhcos-rpm-ostree-updates","truth_value":"IN","reason":"premise"},{"node":"image-layering-verify-rpm-ostree-status","truth_value":"IN","reason":"premise"},{"node":"windows-node-architectural-divergence","truth_value":"IN","reason":"SL justification valid","antecedents":["windows-nodes-not-crio","windows-containers-ovn-hybrid-networking"],"label":"Windows nodes require distinct runtime and networking from Linux nodes"},{"node":"windows-nodes-not-crio","truth_value":"IN","reason":"premise"},{"node":"windows-containers-ovn-hybrid-networking","truth_value":"IN","reason":"premise"}]}}