Motivation

We often get asked if Prometheus Operator can be deployed onto an OCP so that users can create additional monitoring stacks to their liking. This is an unsupported scenario because of the following reasons.

• there is a chance that the newly deployed PO CRDs may break in-cluster monitoring
• The new Operator might also start managing in-cluster monitoring stack CRs

With Observability Operator we worked around this limitations by creating new API group - monitoring.rhobs while keeping the rest of the code/api the same. This epic focuses on releasing the RHOBS fork of PO as a productised (redhat) operator.

Goals

• Observability Operator is installable through community operators