Feature Overview (aka. Goal Summary)

Rebase MicroShift to OpenShift latest and corresponding k8s

Goals (aka. expected user outcomes)

• MicroShift version in lockstep with OpenShift
• Update the version of LVMS used by MicroShift
  • If we'd like to use the latest LVMS version, we need to get access to the development builds of TopoLVM
• Optimize the MicroShift build process with ART
• MicroShift is supported on RHEL 9.x and RHEL 10.x, same versions as OpenShift.

Requirements (aka. Acceptance Criteria):

This release of MicroShift is derived and in lockstep with same OpenShift version, including all dependencies like GO compiler, LVMs etc.

Questions to Answer (Optional):

None

According to current plans (as of 01/2026), 5.0 will NOT be an EUS release. Instead (and unusual for the odd number), V4.23 will have EUS release. That would be highly confusing for MicroShift customers and complicated for the EUS+1 direct upgrade support we have. This leads to the question if we can support MicroShift 5.0 as EUS release, using the branch and code from 4.23 (which might be actually the same, according to current plans). See this visualisation.

Out of Scope

n/a

Background

n/a

Customer Considerations

n/a

Documentation Considerations

Version Matrix needs to be updated as usual

Interoperability Considerations

n/a