-
Story
-
Resolution: Unresolved
-
Normal
-
ACM 2.13.0
Value Statement
To support deployment of VolSync from ACM via a managedClusterAddOn on all managed clusters (OpenShift and non-OpenShift), move the volsync-addon-controller to deploying VolSync as a helm chart.
- Currently we deploy on OpenShift only, as an OLM operator subscription.
- VolSync would be deployed in all cases (OpenShift and non-OpenShift) as a helm chart to be consistent.
- This means we need to remove the OLM operator for OpenShift clusters in addition to deploying the helm chart.
- Helm charts will be embedded with the VolSync operator.
- This means ACM will always package the latest available VolSync release, and volsync updates on managed clusters will happen when ACM is released.
- ACM fixpacks will sometimes update VolSync releases .Y verisons, essentially always moving to the latest available at the time of the ACM fixpack.
- This also means all ACM releases will deploy the same Volsync version (excepting differences when one ACM fixpack hasn't shipped yet that would contain this latest release).
Definition of Done for Engineering Story Owner (Checklist)
- Need to be able to deploy VolSync (using the ManagedClusterAddOn) as a helm chart for managed clusters that are OpenShift
- This also means for existing managedclusters with VolSync installed, the Operator should be removed, no CSV should be present (so only 1 volsync deployment on the managed cluster, the helm chart one
- Need to be able to deploy VolSync (using the ManagedClusterAddOn) as a helm chart for managed clusters that are not OpenShift
- Which cluster types?
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.