-
Story
-
Resolution: Done
-
Undefined
-
None
-
None
-
2
-
False
-
None
-
False
-
-
-
-
GRC Sprint 2023-17
-
No
Value Statement
The Policy Propagator defines a ServiceMonitor and PrometheusRule in the openshift-monitoring namespace, but that openshift-monitoring namespace should be reserved for OpenShift itself. The Governance Framework and Configuration Policy controller both create ServiceMonitors on that namespace as well.
The ask is to create those in the namespace that the controllers are running in and label the controller namespace with "openshift.io/cluster-monitoring" instead.
Definition of Done for Engineering Story Owner (Checklist)
- ...
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.
- blocks
-
ACM-7638 Remove remnants of ACM PrometheusRule and ServiceMonitors from openshift-monitoring namespace
- Closed
-
ACM-7676 Remove and reinstall PrometheusRule and ServiceMonitors from openshift-monitoring namespace to namespace where MCE is deployed
- Closed
- depends on
-
ACM-7637 Configure OCP cluster-monitoring label to namespace where MCH is deployed
- Closed