The etcd operator controller deployment failed

Describe the bug
Helm install failed for release cozy-etcd-operator/etcd-operator with chart [email protected]+a11612f35f31: context deadline exceeded

Environment

Cozystack version: v1.1.0

To Reproduce
Create fresh deployment.

Logs

kubectl logs -n cozy-etcd-operator deployment/etcd-operator-controller-manager -c kube-rbac-proxy
Error from server (BadRequest): container "kube-rbac-proxy" in pod "etcd-operator-controller-manager-666f5796f6-k2q7k" is waiting to start: image can't be pulled

Failed to pull image "gcr.io/kubebuilder/kube-rbac-proxy:v0.16.0": rpc error: code = NotFound desc = failed to pull and unpack image "gcr.io/kubebuilder/kube-rbac-proxy:v0.16.0": failed to resolve reference "gcr.io/kubebuilder/kube-rbac-proxy:v0.16.0": gcr.io/kubebuilder/kube-rbac-proxy:v0.16.0: not found

Additional context
Seems to be related to the cozystack/etcd-operator#271 issue.

Kostiantyn Astakhov (@kastakhov)

Hi Kostiantyn Astakhov (@kastakhov)! I'm Dosu and I’m helping the cozystack team.

This is a known issue tracked in #488. The gcr.io/kubebuilder/kube-rbac-proxy:v0.16.0 image is deprecated and became unavailable from March 18, 2025.

Workaround: You can override the image via Helm values:

kubeRbacProxy:
  image:
    repository: <alternative-registry>/kube-rbac-proxy
    tag: v0.16.0

The long-term fix requires updating etcd-operator to use Controller-Runtime's WithAuthenticationAndAuthorization feature instead of kube-rbac-proxy, as noted in the upstream etcd-operator issue #271 you linked.

To reply, just mention @dosu.

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}