-
Story
-
Resolution: Done
-
Major
-
None
-
None
-
BU Product Work
-
2
-
False
-
None
-
False
-
OCPSTRAT-680 - Integrate Cluster API in standalone OCP-Phase 2
-
-
-
CLOUD Sprint 252, CLOUD Sprint 256, CLOUD Sprint 257, CLOUD Sprint 258, CLOUD Sprint 259, CLOUD Sprint 260, CLOUD Sprint 261
Background
To enable a quick start in CAPI, we want to allow the users to provide just the Machines/MachineSets and the relevant configuration for the Machines. The cluster infrastructure is either not required to be populated, or something they should not care about.
To enable the quick start, we should create and where applicable, populate required fields for the infrastructure cluster.
This will go alongside a generated Cluster object and should mean that the `openshift-cluster-api` Cluster is now infrastructure ready.
Steps
- Create a separate go module in cluster-api-provider-azure/openshift
- Create a controller in the above module Go to manage the AzureCluster resource for non-capi bootstrapped clusters
- Ensure the AzureCluster controller is only enabled for Azure platform clusters
- Create an "externally-managed" AzureCluster resource and manage the status to ensure Machine's can correctly be created
- Populate any required spec/status fields in the AzureCluster spec using the controller
- (Refer to openstack implementation)
Stakeholders
- Cluster Infra
Definition of Done
- AzureCluster resource is correctly created and populated on Azure clusters
- Docs
- <Add docs requirements for this card>
- Testing
- <Explain testing that will be added>
- clones
-
OCPCLOUD-2205 Generate GCPCluster resource for CAPI clusters
- Closed
- is cloned by
-
OCPCLOUD-2207 Generate VSphereCluster resource for CAPI clusters
- Closed
- links to