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