-
Story
-
Resolution: Won't Do
-
Undefined
-
None
-
None
-
None
Value Statement
As an ACM policy user, I need a way to rollout a policy slowly over all my clusters so that I can limit the blast radius.
We mostly get this for free with the placement library but logic of combining placement decisions from multiple placements would need to be supported.
Definition of Done for Engineering Story Owner (Checklist)
- I can use the "Progressive" rollout strategy
- I can use multiple Placements and PlacementBindings with my Policy
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_issue template](
https://github.com/stolostron/backlog/issues/new?assignees=&labels=squad%3Adoc&template=doc_issue.md&title=),
and ensure doc acceptance criteria is met. Link the development issue to
the doc issue. - [ ] Provide input to the QE team, and ensure QE acceptance criteria
(established between story owner and QE focal) are met.
Support Readiness
- [ ] The must-gather script has been updated.
- depends on
-
ACM-7299 Add support for the ProgressivePerGroup rollout strategy
- Closed