-
Story
-
Resolution: Done
-
Critical
-
None
-
None
-
BU Product Work
-
3
-
False
-
None
-
False
-
OCPSTRAT-680 - Integrate Cluster API in standalone OCP-Phase 2
-
-
-
CLOUD Sprint 258, CLOUD Sprint 259, CLOUD Sprint 260, CLOUD Sprint 261, CLOUD Sprint 263, CLOUD Sprint 262
Background
The CAPI operator should ensure that, for clusters that are upgraded into a version of openshift supporting CAPI, that a Cluster object exists in the openshift-cluster-api namespace with the name as the infratructure ID of the Cluster.
The cluster spec should be populated with the reference to the infrastructure object and the status should be updated to reflect that the control plane is initialized.
Steps
- Extend the existing cluster controller to manage the Cluster resource within CAPI operator
- Ensure that on supported platforms it populates a Cluster object for the cluster
- Add documentation to the CAPI operator to describe the controller and its operation
- Add testing to track the operation of the controller
- Ensure the controller does not interfere with Cluster resources that were not created by it
Stakeholders
- Cluster Infra
Definition of Done
- When I install a tech preview cluster, I should be able to `oc get cluster -n openshift-cluster-api` and have a result returned without any action on my part
- Docs
- <Add docs requirements for this card>
- Testing
- <Explain testing that will be added>