-
Story
-
Resolution: Done
-
Major
-
None
-
None
-
BU Product Work
-
5
-
False
-
None
-
False
-
OCPSTRAT-680 - Integrate Cluster API in standalone OCP-Phase 2
-
-
-
CLOUD Sprint 252, CLOUD Sprint 253, CLOUD Sprint 254, CLOUD Sprint 255, CLOUD Sprint 256, CLOUD Sprint 257
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 new infracluster controller in cluster-capi-operator
- Implement the common logic for all the providers within the controller
- Set up testing environment for the new controller
- Define integration tests for the new controller
Stakeholders
- Cluster Infra
Definition of Done
- InfraCluster controller is created in the cluster-capi-operator repository
- Docs
- <Add docs requirements for this card>
- Testing
- <Explain testing that will be added>
- clones
-
OCPCLOUD-2207 Generate VSphereCluster resource for CAPI clusters
- Closed
- links to