metallb 4.12.0-202301042354 (OCP 4.12) refers to external image

metallb 4.12.0-202301042354 (OCP 4.12)  refers to external image `gcr.io/kubebuilder/kube-rbac-proxy:v0.12.0` 

OCP 4.12.0
metallb 4.12.0-202301042354

follow docs and install metallb https://docs.openshift.com/container-platform/4.12/networking/metallb/metallb-operator-install.html

1. Install metallb via WEB UI or via cli as outlined in docs 
2. Deploy MetaLB CR
3. check used images 

Ds and deploy controller reference `gcr.io/kubebuilder/kube-rbac-proxy:v0.12.0`  instead of an image on quay or redhat registry

```
[root@jump ~]# oc get deploy controller -o yaml |grep image 
        image: registry.redhat.io/openshift4/metallb-rhel8@sha256:649dc3e7bbc3fa9552f25727e45cdb2e6db2a3011003476654ec414cf978a41d
        imagePullPolicy: IfNotPresent
        image: gcr.io/kubebuilder/kube-rbac-proxy:v0.12.0
        imagePullPolicy: IfNotPresent
[root@jump ~]# 
# oc get ds -o yaml  |grep image 
...
          image: gcr.io/kubebuilder/kube-rbac-proxy:v0.12.0
          imagePullPolicy: IfNotPresent
          image: gcr.io/kubebuilder/kube-rbac-proxy:v0.12.0
          imagePullPolicy: IfNotPresent
...
```
Which is causing issues for disconnected and environmants where none standard registries are blocked 

appropriate image from a Red Hat owned registry is referred to, e.g. `registry.redhat.io/openshift4/ose-kube-rbac-proxy@sha256:cb836456974e510eb4bccbffadbc6d99d5f57c36caec54c767a158ffd8a025d5`

Would be good if we can find a workaround to replace the image by an appropriate one until this is officially fixed