Value Statement

In ACM 2.9, RHACM will begin deploying Service Monitors and PrometheusRules resources in the same namespace as the MCH resource. By adding the openshift.io/cluster-monitoring: "true" label, this will allow customers to add their own Service Monitors/PrometheusRules to the namespace, which will allow OCP to find those resources outside of the `openshift-monitoring` namespace.

In ROSA/managed service environments, customers do not have permission to write into the `openshift-monitoring` namespace; therefore, by applying the OpenShift label to the MCH namespace, this will allow those resources to be discovered.

Definition of Done for Engineering Story Owner (Checklist)

• [x] By default, the openshift.io/cluster-monitoring: "true" label is added to the namespace where MCH is deployed on the hub cluster.
• [x] After upgrade from ACM 2.8 > 2.9, the label is present on the MCH namespace.

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [x] Unit/function tests have been automated and incorporated into the
  build.
• [x] 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.