Description of problem:

After installing TALM with user workload monitoring enabled the PrometheusOperatorRejectedResources alert is active.

From the user workload prometheus operator pod the following log message:

level=warn ts=2024-04-04T15:30:37.381302569Z caller=resource_selector.go:174 component=prometheusoperator msg="skipping servicemonitor" error="it accesses file system via bearer token file which Prometheus specification prohibits" servicemonitor=openshift-operators/cluster-group-upgrades-controller-manager-metrics-monitor namespace=openshift-user-workload-monitoring prometheus=user-workload

Version-Release number of selected component (if applicable):

4.14

How reproducible:

Every time

Steps to Reproduce:

    1.Enable user workload monitoring
    2. Install TALM Operator
 
    

Actual results:

    level=warn ts=2024-04-04T15:30:37.381302569Z caller=resource_selector.go:174 component=prometheusoperator msg="skipping servicemonitor" error="it accesses file system via bearer token file which Prometheus specification prohibits" servicemonitor=openshift-operators/cluster-group-upgrades-controller-manager-metrics-monitor namespace=openshift-user-workload-monitoring prometheus=user-workload

Expected results:

    Cluster monitoring scrapes TALM metrics

Additional info:

Error is raised because "openshift-operators" namespace is not labeled for cluster monitoring.  Please consider changing the instructions to install the operator to a namespace owned by TALM Operator, as OpenShift GitOps has recently done.