Value Statement

In ACM 2.9, RHACM will begin deploying its Service Monitors and PrometheusRules resources in the same namespace as the MCH resource.

MCH will remove the previously created ACM Service Monitors/PrometheusRules that are located in the `openshift-monitoring` namespace and reapply them into the namespace where MCH is located. This will prevent customers from attempting to write into the `openshift-monitoring` namespace on ROSA/managed service environments, where they not permitted to do so.

Definition of Done for Engineering Story Owner (Checklist)

• [x] MCH removes `Service Monitors` resources from openshift-monitoring namespace and applies them into the desired MCH namespace.
• [x] MCH removes `PrometheusRule` resources from openshift-monitoring namespace and applies them into the desired MCH namespace.
• [x] Resources are removed before upgrade occurs.

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.