Status: IN
OpenShift update strategies (canary rollouts via custom MCPs and EUS-to-EUS skips for even minor versions) operate strictly within the platform's lifecycle boundaries — install-time decisions constrain what can be updated, and version coupling determines the order and scope of what canary pools can validate.
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
Depends on (SL): platform-lifecycle-bounded-at-install-and-update, update-strategy-canary-and-control-plane-model