Description of problem:

With OpenShift GitOps 1.10, the default namespace for the GitOps Operator has been changed to "openshift-gitops-operator". However, existing installations still use the old default "openshift-operators" namespace.

The issue and workaround (manually update the ServiceMonitor) is documented here: https://access.redhat.com/solutions/7036961

However, we should be backwards-compatible and this should be done automatically by the Operator. I would expect that when an existing OpenShift GitOps installation is updated from 1.9 to 1.10, there are no errors or issues arising from that. OpenShift GitOps should also work without errors when installed in the "openshift-operators" namespace (as it was default in < 1.9).

Prerequisites (if any, like setup, operators/versions):

Steps to Reproduce

1. On OpenShift Container Platform, install OpenShift GitOps 1.9 and install it in the default "openshift-operators" namespace
2. Upgrade to OpenShift GitOps 1.10

Actual results:

After upgrade, an PrometheusOperatorRejectedResources alert is firing, need to apply the steps outlined in https://access.redhat.com/solutions/7036961 to fix it

Expected results:

No errors or additional alerts are shown, the old namespace works as expected

Reproducibility (Always/Intermittent/Only Once):

Always

Acceptance criteria: 

Definition of Done:

Build Details:

Additional info (Such as Logs, Screenshots, etc):

• Solution article: https://access.redhat.com/solutions/7036961
• Discussion on Slack:[ https://redhat-internal.slack.com/archives/CMP95ST2N/p1696276860900959|https://redhat-internal.slack.com/archives/CMP95ST2N/p1696276860900959]