-
Story
-
Resolution: Done
-
Undefined
-
None
-
5
-
False
-
None
-
False
-
-
ACM-8968 - Event driven ConfigurationPolicy
-
-
-
GRC Sprint 2024-10, GRC Sprint 2024-11, GRC Sprint 2024-12, GRC Sprint 2024-13
-
No
Value Statement
As a policy user, I would like ConfigurationPolicy to be event-driven so that it responds immediately to objects changing on the cluster including template results.
This will improve performance and resource utilization overall (Kubernetes API and config-policy-controller).
Definition of Done for Engineering Story Owner (Checklist)
- The existing evaluationInterval defaults to watch unless overridden.
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.
- is documented by
-
ACM-14388 Document event driven ConfigurationPolicy
- Closed
- links to
-
RHEA-2024:138972 OpenShift Container Platform 4.17.0 ORAN O2IMS extras update
- mentioned on
(2 mentioned on)