-
Feature
-
Resolution: Done
-
Critical
-
None
-
None
-
Upstream
-
True
-
-
50% To Do, 0% In Progress, 50% Done
-
1
-
0
-
Program Call
Feature Overview (aka. Goal Summary)
As Service consumer persona I can use CAPI to introduce customization for cluster update/upgrade strategy. Add new fields in CAPA will allow multiple cluster nodes to be upgraded in parallel and helping to reduce the overall upgrade time. Enable Service Consumer personas to lifecycle managed OpenShift (ROSA with Hosted Control Planes) via CAPI. This Feature covers the Demo-3 for the customer. Previous demos were covered by OCPSTRAT-760, OCPSTRAT-1139
Acceptance criteria.
- As a Service Consumer, I should use upstream CAPI to provision ROSA+HCP cluster as covered by
OCPSTRAT-760,OCPSTRAT-1139 - Following features should be supported by CAPI by June 1:
- worker upgrades with maxunavail/maxsurge/nodedraininggraceperiod ( June 1)
- Customers can pass a non-zero value for Node Pool parameter maxUnavailable at a cluster level that will be used during the cluster upgrade to upgrade as many nodes in parallel. This will allow parity between self-managed OCP and ROSA/OSD clusters.
- worker upgrades with maxunavail/maxsurge/nodedraininggraceperiod ( June 1)
Out of Scope for this feature .
Below are out of scope and will be delivered after June 1
-
- OCPSTRAT-787 Adding user-tags day-2 support (Q4)
- XCMSTRAT-371 Clusters should support larger worker nodes(250+)
- XCMSTRAT-122 arm64 support (Q2 2024)
- XCMSTRAT-769 Priority expander support in ROSA HCP(August in 4.16.z)