-
Story
-
Resolution: Won't Do
-
Undefined
-
None
-
None
Value Statement
As an ACM policy user, I would like to track the rollout status of a policy that has been created or updated so that I can know when all clusters have reported in.
Definition of Done for Engineering Story Owner (Checklist)
- Start using the new placement decision library
- Only support the "All" rollout strategy as defined with the Policy's spec.rolloutStrategy.type=All field which is the default and only value for now.
- The config-policy-controller sets the "policy.open-cluster-management.io/last-evaluated-generation" annotation on policy status events.
- The status sync sets the "rolloutStatus" field on the propagated policy on the managed cluster and hub to "Succeeded" when the ConfigurationPolicy is compliant and the policy status event "policy.open-cluster-management.io/last-evaluated-generation" annotation matches the current ConfigurationPolicy generation. This never sets "Failed". That will happen once the "timeout" functionality is implemented later.
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-7295 Add a rollout status field on the Policy CRD
- Closed
- is depended on by
-
ACM-7304 Support viewing the policy rollout progress in the console
- Closed
-
ACM-7299 Add support for the ProgressivePerGroup rollout strategy
- Closed
-
ACM-7300 Add a "timeout" during a progressive policy rollout
- Closed
-
ACM-7302 Support setting clusters as "best effort" for a policy rollout
- Closed