-
Story
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
BU Product Work
-
False
-
None
-
False
-
OCPSTRAT-132 - [Tech Preview] Cluster API Provider for Azure
-
-
-
CLOUD Sprint 255, CLOUD Sprint 256, CLOUD Sprint 257, CLOUD Sprint 258, CLOUD Sprint 259, CLOUD Sprint 260, CLOUD Sprint 261, CLOUD Sprint 262
User Story
The Cluster API provider Azure has a deployment manifest that deploys Azure service operator from mcr.microsoft.com/k8s/azureserviceoperator:v2.6.0 image.
We need to set up OpenShift builds of the operator and update the manifest generator to use the OpenShift image.
Background
Azure have split the API calls out of their provider so that they now use the service operator. We now need to ship service operator as part of the CAPI operator to make sure that we can support CAPZ.
Steps
Request for the ASO repo to be created and build in Openshift- Set up release repo configuration and basic testing for ASO repo
- Set up ART build for ASO repo
- Update the manifest generator in cluster-capi-operator to replace the image with our image stream.
- Manifest generator should know how to filter parts of ASO so that we only ship the parts of Azure care about
- Create manifests for deploying the subset of required ASO that we need
Stakeholders
- Cluster Infrastructure
Definition of Done
- CAPZ deploys OpenShift version of ASO
- Docs
- Testing
- blocks
-
OCPCLOUD-2745 Rebase/update to K8s 1.30 for Cluster API Provider Azure
- In Progress
- links to
(1 links to)