-
Epic
-
Resolution: Unresolved
-
Critical
-
None
-
Openshift 5.0 readiness
-
False
-
-
False
-
Not Selected
-
To Do
-
100% To Do, 0% In Progress, 0% Done
Epic Goal
This epic is for Openshift 5.0 readiness
Why is this important?
Execute the transition of OpenShift Builds to OpenShift 5.0.
The primary objective is to achieve GA on RHCOS 10 while maintaining full support for RHCOS 9 (via OCP 4.22/4.23 and 5.0/5.1 upgrades).
Per stakeholder guidance, OLM v0 will remain the supported engine for the 5.0 launch, with OLM v1 adoption targeted for the OCP 5.2 timeframe.
Development will focus on "Dual Stream" host support and maintaining UBI 9 container images to ensure FIPS/PQC compliance until OCP 5.3.
| Milestone | Date | Host OS Focus | OLM Status |
| OCP 5.0 GA | Oct 2026 | RHCOS 10 (New) / RHCOS 9 (Upgrades) | OLM v0 (Default) |
| OCP 5.1 | Feb 2027 | Mixed RHCOS 9/10 Support | OLM v0 |
| OCP 5.2 | Jun 2027 | End of RHCOS 9 support | OLM v1 Readiness / v0 Deprecation Start |
Resources:
- Preview: Red Hat OpenShift 5 Intent to Release Roadmap Update
- RHCOS 10 Readiness Tracking
- OpenShift 5 Guidance for OLM-managed Operators
- https://issues.redhat.com/browse/OCPSTRAT-2558
Done Checklist
- Acceptance criteria are met
- Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
- User Journey automation is delivered
- Support and SRE teams are provided with enough skills to support the feature in production environment