-
Story
-
Resolution: Done
-
Major
-
None
-
None
-
3
-
False
-
None
-
False
-
-
ACM-955 - ROSA HCP lifecycle management via CAPA
-
-
-
CAPI Sprint 2024-23, CAPI Sprint 2024-24, CAPI Sprint 2024-25
-
None
Value Statement
We need to create a helm chart for the down stream cluster-api repo based on the default config directory [here|https://github.com/openshift/cluster-api/tree/master/config]
- The helm chart must contain the deployment, CRDs (each crd in different file), service, webhookValidation and required Roles.
- The resources namespace should be changeable through the chart value file and default to capi-system
- Initially The chart should be created in the cluster-api-installer repo https://github.com/stolostron/cluster-api-installer/
Definition of Done for Engineering Story Owner (Checklist)
- ...
Development Complete
- The code is complete.
- Functionality is working.
- Any required downstream Docker file changes are made.
Tests Automated
- [ ] Unit/function tests have been automated and incorporated into the
build. - [ ] 100% automated unit/function test coverage for new or changed APIs.
Secure Design
- [ ] Security has been assessed and incorporated into your threat model.
Multidisciplinary Teams Readiness
- [ ] Create an informative documentation issue using the Customer
Portal Doc template that you can access from [The Playbook](
and ensure doc acceptance criteria is met.
- Call out this sentence as it's own action:
- [ ] Link the development issue to the doc issue.
Support Readiness
- [ ] The must-gather script has been updated.
- blocks
-
ACM-15664 As an Installer dev, I want to onboard the CAPI component into our chart automation to generate a deployment ready template chart for the MCE operator to manage
-
- Closed
-
- is depended on by
-
ACM-13577 As an MCE dev, I want to add a toggle for the CAPI deployment in the MCE backplane-operator, allowing users to enable or disable the component in the MCE CR
-
- Closed
-