Status: IN
OpenShift enforces strict version coupling and update ordering: CNV minor version must match OCP minor version, OCP must update before CNV, HCP follows a three-step update sequence (management OCP → MCE → hosted cluster), and rollback is never supported — creating a unidirectional, order-dependent upgrade graph.
Version coupling rules and forward-only updates form a strict upgrade governance model
Depends on (SL): cnv-version-must-match-ocp-version, cnv-update-ocp-first-then-cnv, hcp-update-order-management-mce-hosted, ocp-rollback-not-supported