Value Statement

RHACM Observability today configures Service Monitors and PrometheusRule resources into openshift-monitoring namespace so that these resources are discovered by Platform Prometheus. However, in ROSA/managed service environments, customers do not have permission to write into {{openshift-monitoring }}namespace. This prevents these clusters from being configured as ACM hubs by an customer. 

We want to move to a model that is supported long term, both for standalone OCP and managed OCP clusters taking into account the upgrade scenarios as described in the parent epic.

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.