Feature Overview (aka. Goal Summary)  

OCP 4.19 is switching to RHEL 9.6 (EUS release) . Hence MicroShift needs to switch, too.

MicroShift V4.19 will be supported on RHEL 9.6 and RHEL 10.x 

Goals (aka. expected user outcomes)

Requirements (aka. Acceptance Criteria):

1. Support MicroShift V4.19 on RHEL 9.6 X86 and ARM
2. Older MicroShift versions (4.14 and 4.15) will remain unchanged in their support policy, i.e. they stay on RHEL 9.4
3. Support upgrade from supported previous combinations to current one. That is: 4.18+9.4 -> 4.19+9.6 and 4.17+9.4 -> 4.19 / 9.6 
4. Only a direct and simultaneous upgrade of BOTH  MicroShift and RHEL is supported. This needs to be especially highlighted in the upgrade documentation, because there is a danger on rpm based systems to just do a `dnf update`, which would give you an upgrade to RHEL 9.6, bot NOT MicroShift 4.19, as this requires to manually change to the OCP 4.16 rpm repos.
5. If technically possible, it would be good to protect users against this, e.g. by adding suitable dependency to V4.19 rpms that would block an update to RHEL 9.6. 

Out of Scope

• Support for older RHEL versions
• Stepwise upgrade. E.g. upgrade first to 4.16 on RHEL 9.2, then upgrade to RHEL 9.4. The first step would result in an unsupported config (4.16 on RHEL 9.2) and is not supported.

Background

MicroShift & RHEL Combinations Support Policy Considerations

Customer Considerations

Documentation Considerations

Release compatibility matrix and installation instructions need to be updated.

Interoperability Considerations

• none

Open Questions

• none