Status: IN
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.
Update strategies assume orderly rollout but the fleet is fundamentally heterogeneous — combining reveals the tension between progressive updates and fleet diversity.
Depends on (SL): progressive-update-within-lifecycle-bounds, lifecycle-constrained-across-heterogeneous-fleet