Undefined The feature is starting as placeholder for tracking this activity and gathering requirements. It will evolve to a proper requirements issue
==
ACS 5.0 vision ( source ) includes:
RHACS will become a platform-aligned operator with OCP 5, targeting the October 2026 release. This deeper integration aims for a more unified experience and simplified management. Release once a week with fast stream as OCP but align releases with OCP releases
References:
- OpenShift.Next
- Standardizing Lifecycle of Layered Products
- OpenShift 4 vs. 5 Lifecycle Comparison
- ACM - Support Extension to a 3-year EUS
- Criteria for moving support from the OCP eng team to Sustaining Engineering
10/29/2025
- Initial discussion with msugakov@redhat.com on understanding the differences between tier 1 and 2
- There are early thoughts on setting this up as a shared effort under eparis@redhat.com's organization, maybe even a sustainability team
- Misha will analyze the costs ( effort and infrastructure) in case the ACS team is tasked with it entirely on our won
- Noted that multi cluster brings about interesting support matrix cases. Do we allow customers running an old version to secure new clusters?
- Imagine 4.7 is EUS :
| OCP version (Central) | ACS Central version | OCP version (secured cluster) | ACS Secured cluster version | Supported ? |
|---|---|---|---|---|
| old 4.7 | old 4.7 | old 4.7 | old 4.7 | yes |
| old 4.7 | old 4.7 | old 4.7 | new 4.15 | ? |
| old 4.7 | old 4.7 | new 4.15 | old 4.7 | ? |
| old 4.7 | old 4.7 | new 4.15 | new 4.15 | ? |
- Boaz reached out to ACM team. sberens@redhat.com offered to work on this together
