-
Epic
-
Resolution: Done
-
Blocker
-
None
-
Placement - support progressive rollout strategies
-
False
-
None
-
False
-
Green
-
To Do
-
ACM-944 - Workload Delivery and Scheduling
-
0% To Do, 0% In Progress, 100% Done
Epic Goal
Support a rollout strategy in the Placement API to allow for consumers to progressively apply their content to managed clusters
https://github.com/open-cluster-management-io/enhancements/pull/88/files
Why is this important?
- Increasingly in scenarios there is a need to control the rollout of workloads and manifests from the hub across clusters
- In
ACM-1717, there is a requirement to support a progressive rolling upgrade of the ACM management add-ons - In other scenarios, there are requirements from end-users to support a "canary" rollout of changes from Configuration Policies
- In
Scenarios
...
Acceptance Criteria
...
Dependencies (internal and external)
- ...
Previous Work (Optional):
- ...
Open questions:
- …
Done Checklist
- CI - CI is running, tests are automated and merged.
- Release Enablement <link to Feature Enablement Presentation>
- DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
Issue> - DEV - Upstream documentation merged: <link to meaningful PR or GitHub
Issue> - DEV - Downstream build attached to advisory: <link to errata>
- QE - Test plans in Polarion: <link or reference to Polarion>
- QE - Automated tests merged: <link or reference to automated tests>
- DOC - Downstream documentation merged: <link to meaningful PR>
- blocks
-
ACM-5653 RFE Policy support for progressive rollout strategies
-
- New
-
