+++ This bug was initially created as a clone of Bug #1893784 +++
+++ This bug was initially created as a clone of Bug #1893724 +++
Description of problem:
When using the OperatorHub Console to install an operator that supports reporting metrics to Telemeter the generated Service RoleBinding is created for the `prometheus-operator` ServiceAccount  instead of the `prometheus-k8s` ServiceAccount, preventing prometheus from scraping the operator's metrics.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install an operator which includes the `operatorframework.io/cluster-monitoring=true` annotation.
The operator is installed but the Prometheus Service RBAC is generated for the `prometheus-operator` ServiceAccount.
The operator is installed and the Prometheus Service RBAC is generated for the `prometheus-k8s`ServiceAccount.
1. Install Metering operator which has `operatorframework.io/cluster-monitoring=true` annotation
2. Check the rolebinding openshift-metering-prometheus, it is subjected to 'prometheus-k8s' serviceaccount
- kind: ServiceAccount
Verified on 4.5.0-0.nightly-2020-11-13-045120
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Moderate: OpenShift Container Platform 4.5.20 bug fix and golang security update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.