From this upstream controller-runtime issue it looks like we can remove all use of kube-rbac-proxy . It is recommended to leverage the built-in WithAuthenticationAndAuthorization filter in controller-runtime: https://book.kubebuilder.io/reference/metrics#how-the-metrics-endpoint-can-be-protected-
 
Use of kube-rbac-proxy

• This is used to protect the metrics endpoint exposed by the operator.

Acceptance Criteria

• Remove all occurrences of  the sidecar container using kube-rbac-proxy/ ose-kube-rbac-proxy images from the Operator Deployment
• Leverage the built-in WithAuthenticationAndAuthorization filter to protect the /metrics endpoint
• Regenerate the bundle manifests
• Everything works as before.
  • Check if the /metrics endpoint is used (perhaps from OpenShift Monitoring) and if metrics still show up

Testing

• create a Pod that curls this endpoint
• make sure only pods with the right K8s service account role can access this endpoint

If successful, RHIDP-2830 can be closed as won't do, since this eliminates the need for the extra container in the CSV.