+++ 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. cluster admin user subscribe Metering operator which has `operatorframework.io/cluster-monitoring=true` annotation
2. check openshift-metering-prometheus rolebinding
$ oc describe rolebinding openshift-metering-prometheus -n openshift-metering
Kind Name Namespace
---- ---- ---------
ServiceAccount prometheus-k8s openshift-monitoring
The operator is installed and the Prometheus Service RBAC is generated for the `prometheus-k8s`ServiceAccount
Verified on 4.6.0-0.nightly-2020-11-07-035509
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 (OpenShift Container Platform 4.6.4 bug fix 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.