-
Feature
-
Resolution: Done
-
Major
-
None
-
None
-
Future Sustainability
-
-
0% To Do, 0% In Progress, 100% Done
-
None
-
None
-
None
-
None
-
None
-
None
-
-
-
-
None
-
None
-
None
-
None
Feature Overview (aka. Goal Summary)
Enable Service Consumer personas to lifecycle managed OpenShift (ARO with Hosted Control Planes) via CAPI.
Goal
- As a Service Consumer, I want to be able to provision and lifecycle HCP clusters (on ARO)
- As a Service Consumer, I want to CRUD cluster with some tweak knobs (TBD), upgrade control plane, CRUD machine pools.
Acceptance criteria.
As a Service Consumer, I should use upstream CAPI to provision ARO+HCP cluster. As part of this account-wide roles and OIDC configuration should be done by CAPI.
Following features should be supported by CAPI:
- 54 character cluster name,
- internal & BYO identity support,
- user-tags support,
- crio-o logging passthruough ,
- set max node grace period (nodeDrainGracePeriod)to 1 week,
- private cluster,
- get status of clusters,
- machinepool & controlplane updates,
- delete cluster.
- No CNI mode with Cilium
- security groups & resource tags
- >15 character cluster name
- Clusters should support larger worker nodes(250+)
- arm64 support
- blocks
-
ACM-6719 RFE Deployment of ARO from ACM using existing CRDs or new ones if needed
-
- Closed
-
- clones
-
RFE-4244 Add support for clusterapi with ARO
-
- Backlog
-
- depends on
-
ACM-21406 CAPZ upstream implementation for ARO HCP features for ACM 2.15
-
- In Progress
-
-
OCPSTRAT-987 Hosted Control Planes is seamlessly integrated as a backend for ARO
-
- In Progress
-
- is cloned by
-
OCPSTRAT-760 [Upstream] CAPI provider for ROSA with HCP - Phase 1 (MVP-1 / Demo)
-
- Closed
-
- is duplicated by
-
OCPSTRAT-1799 [Upstream] CAPI provider for ARO with HCP - Phase 1
-
- Closed
-
- is related to
-
RFE-4077 ROSA/ARO Support for Cluster API open source project
-
- Approved
-
- links to