-
Story
-
Resolution: Done
-
Undefined
-
ACM 2.12.0
-
2
-
False
-
None
-
False
-
-
ACM-12484 - Standalone Policy deployment & enhanced GitOps integration
-
-
-
GRC Sprint 2024-18
-
None
Value Statement
As a standalone policy user, I'd like to deploy my policies to the same namespace on every managed cluster rather than dynamically determine the managed cluster namespace name for each cluster.
Definition of Done for Engineering Story Owner (Checklist)
- The config-policy-controller and cert-policy-controller have their WATCH_NAMESPACE environment variable include the manged cluster namespace and "open-cluster-management-policies".
- The RBAC is updated in the controllers to account for this namespace when NOT in hosted mode.
- Hosted mode does not watch this namespace.
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.
- is documented by
-
ACM-14599 Document the standalone/discovered policies feature
- Closed