The image for the container `gcr.io/kubebuilder/kube-rbac-proxy` is not available.

Which component(s) is affected?

Operator

Describe the bug

When installing via kubero install or kubectl apply -f, the kubero-operator-controller-manager pod does not start because one of the containers is missing from the gcr.io/kubebuilder registry.

I manually changed:

gcr.io/kubebuilder/kube-rbac-proxy:v0.11.0

to:

registry.k8s.io/kubebuilder/kube-rbac-proxy:v0.11.0

and the operator started successfully.

Steps to reproduce

No response

Expected behavior

All pods should start successfully when running kubero install.

Screenshots

No response

Additional information

No response

Debug information

Kubero CLI
kuberoCLIVersion: v2.4.0
OS: darwin
Arch: arm64
goVersion: go1.21.13

Kubernetes
clientVersion:
  buildDate: "2025-02-12T21:26:09Z"
  compiler: gc
  gitCommit: 67a30c0adcf52bd3f56ff0893ce19966be12991f
  gitTreeState: clean
  gitVersion: v1.32.2
  goVersion: go1.23.6
  major: "1"
  minor: "32"
  platform: darwin/arm64
kustomizeVersion: v5.5.0
serverVersion:
  buildDate: "2026-04-23T03:17:03Z"
  compiler: gc
  gitCommit: 02c854fd37dbe8eef085f7368a346707ba7ebbca
  gitTreeState: clean
  gitVersion: v1.35.4-eks-40737a8
  goVersion: go1.25.9
  major: "1"
  minor: "35"
  platform: linux/amd64

Search the repository's Kubernetes manifests and install entry points for gcr.io/kubebuilder/kube-rbac-proxy:v0.11.0; start by checking the controller-manager deployment used by kubero install and kubectl apply -f. Update the affected image reference and verify that the operator pod starts successfully through both installation paths.