-
Feature
-
Resolution: Unresolved
-
Critical
-
None
-
None
-
100% To Do, 0% In Progress, 0% Done
-
1
-
0
-
0
Feature Overview (aka. Goal Summary)
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
Goal
Infuse upstream CAPI with ROSA+HCP Support. Add BYO-OIDC , AWS tags, and Security group to Machinepools support via CAPI.
Target: May 24th
========
Considerations
Once ROSACluster CRD is implemented in upstream to manage ROSA clusters, downstream bits are to be implemented to integrate with OpenShift/ROSA.
ROSA managed by Capi = ROSA -> ocm api -> hypershift api -> capi -> nodes
the ROSA CAPI Provider will speak to the OCM API via github.com/openshift-online/ocm-sdk-go. The ROSA CLI cannot communicate to OCM via CAPI directly because OCM does not expose a Kubernetes CAPI Server (that would not scale). Instead, the user is expected to run a Kubernetes CAPI environment in their computing environment from which they wish to reconcile.
The initial request from the customer was to use CAPI as their authoritative source of truth for all their cluster fleet.This feature covers other bits like modify machinepools, auth-provider etc.
Acceptance criteria.
- As a Service Consumer, I should use upstream CAPI to provision ROSA+HCP cluster as covered by
OCPSTRAT-760, OCPSTRAT-1139 & OCPSTRAT-1351 - Following features should be supported by CAPI 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)(Q2 2024)
- depends on
-
XCMSTRAT-769 ROSA-HCP: enable cluster autoscaler expanders
- New
-
OCPSTRAT-787 Configure AWS User Tags on Day 2 (Hosted Control Planes only)
- Refinement
- incorporates
-
HOSTEDCP-1551 [Upstream MVP-3] ROSA implementation for Cluster API
- In Progress