Description of problem:

After installing Builds for Red Hat OpenShift operator without checking the box "Enable Operator recommended cluster monitoring on this Namespace", then PrometheusOperatorRejectedResources is streamed.{}

Workaround

$ oc label ns openshift-builds openshift.io/cluster-monitoring=true

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

Builds for Red Hat OpenShift operator 1.1.0

Steps to Reproduce

1. Enable User Workload Monitoring
2. Install Builds for Red Hat OpenShift operator and make sure to skip checking the box "Enable Operator recommended cluster monitoring on this Namespace".
3. After the operator gets installed, the alert PrometheusOperatorRejectedResources starts to stream.

Actual results:

PrometheusOperatorRejectedResources alert streaming if "Enable Operator recommended cluster monitoring on this Namespace" is not checked while operator installation.

Expected results:

PrometheusOperatorRejectedResources should not stream even if "Enable Operator recommended cluster monitoring on this Namespace" is not checked while installation.

Reproducibility (Always/Intermittent/Only Once):

Always

Acceptance criteria: 

Definition of Done:

Build Details:

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

Prometheus operator in openshift-user-workload-monitoring project streams below error as well:

level=warn ts=2024-09-04T11:53:10.166388562Z caller=resource_selector.go:126 component=prometheus-controller msg="skipping servicemonitor" error="it accesses file system via bearer token file which Prometheus specification prohibits" servicemonitor=openshift-builds/shared-resource-csi-driver-node-monitor namespace=openshift-user-workload-monitoring prometheus=user-workload