redhat-cop/resource-locker-operator

Operator broke on OKD and Kubernetes

aelbarkani opened this issue · 4 comments

Hi,

There was a change in the image which breaks the operator for non Redhat users:

image: registry.redhat.io/openshift4/ose-kube-rbac-proxy@sha256:6d57bfd91fac9b68eb72d27226bc297472ceb136c996628b845ecc54a48b31cb

Is there any way I can support a fix of the recent change?

It looks like the discussion points towards a quick-fix to un-break the operators, likewise on redhat-cop/cert-utils-operator#102.

We could change the kube-rbac-proxy image to quay.io/openshift/origin-kube-rbac-proxy as mentioned in redhat-cop/namespace-configuration-operator#118, and then automatically get multiarch support once it's implemented in OKD4.

Additionally, we could undo #56 - and redo it once the multiarch image has been released?

I'd happily submit a PR, but like to align with the maintainers first.

#59 fixes this issue, I can confirm this. Thank you @raffaelespazzoli.