# Operator 2.19.1 not starting completely

**URL:** <https://forum.ansible.com/t/operator-2-19-1-not-starting-completely/45644>\
**Category:** Get Help\
**Tags:** awx, ee, kubernetes\
**Created:** [April 7, 2026, 6:40am UTC](https://forum.ansible.com/t/operator-2-19-1-not-starting-completely/45644 "2026-04-07T06:40:06Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![kurokobo](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/kurokobo/32/182_2.png) [@kurokobo](https://forum.ansible.com/u/kurokobo)\
**Post date:** [April 7, 2026, 8:31am UTC](https://forum.ansible.com/t/operator-2-19-1-not-starting-completely/45644/2 "2026-04-07T08:31:24Z")

</div>

@ildjarn  
Hi,

> [@ildjarn](#):
>
> Is this a temporary problem on the side of [gcr.io](http://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:

```yaml
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.

---

_[View the full topic](https://forum.ansible.com/t/operator-2-19-1-not-starting-completely/45644)._