Operator 2.19.1 not starting completely

[kurokobo]

@ildjarn
Hi,

@ildjarn

Is this a temporary problem on the side of gcr.io or is this version of kube-rbac-proxy no longer supported?

The kube-rbac-proxy image on gcr.io has already been discontinued, so you should replace it with the drop-in replacement from another registry, such as quay.io/brancz/kube-rbac-proxy.
I don’t know how you’ve deployed your AWX Operator, but if you’ve used kustomization.yaml, adding the following to your configuration may solve the issue:

images:
  - name: quay.io/ansible/awx-operator
    newTag: 2.19.1
  - name: gcr.io/kubebuilder/kube-rbac-proxy     👈👈👈
    newName: quay.io/brancz/kube-rbac-proxy     👈👈👈

@ildjarn

And what are the exact consequences if this proxy can’t start? The web and task pods are running, automation-job pods are created when running a job, and as far as I can see everything seems to work fine.

This proxy provides RBAC for the /metrics endpoint of the AWX Operator.
In other words, if you don’t use any Prometheus in the same cluster to gather metrics from the AWX Operator (not from AWX itself), this proxy is not used in your environment.