Status: IN
OpenShift lifecycle management operates under version governance at both ends: progressive updates (canary rollouts, EUS-to-EUS skips) and disaster recovery (etcd backup/restore) are both constrained by the same version coupling rules — recovery cannot escape the boundaries that updates must respect.
Both depth-2 nodes depend on version-coupling-and-update-governance; combining reveals that DR is not an escape hatch from lifecycle constraints but is subject to the same version boundaries as normal operations
Depends on (SL): disaster-recovery-within-version-governance, platform-lifecycle-bounded-at-install-and-update