gcr.io/kubebuilder/kube-rbac-proxy discontinued

Which component(s) is affected?

Operator

Describe the bug

When doing a vanilla install of the operator (kubectl apply -f https://raw.githubusercontent.com/kubero-dev/kubero-operator/main/deploy/operator.yaml) a Deployment is created with a container running gcr.io/kubebuilder/kube-rbac-proxy:v0.11.0. This image cannot be pulled because the entire repo kubebuilder/kube-rbac-proxy has been deleted.

According to the authors:

Starting with release 3.15.0, Kubebuilder will no longer scaffold new projects with kube-rbac-proxy. Existing users are encouraged to switch to images hosted by the project on quay.io OR to adapt their projects to utilize Network Policies, following the updated scaffold guidelines.

Steps to reproduce

kubectl apply -f https://raw.githubusercontent.com/kubero-dev/kubero-operator/main/deploy/operator.yaml

Expected behavior

Deployment healthy

Screenshots

Additional information

Possibly #225 could negate the need for the kube-rbac-proxy sidecar?

Debug information

As a workaround, I've changed the container's image to the recommended replacement, quay.io/brancz/kube-rbac-proxy:v0.21.2. Deployment is now healthy and Kubero works!

Start with deploy/operator.yaml, which is used by the vanilla kubectl apply command, and locate the kube-rbac-proxy container image. Compare it with the recommended quay.io replacement, then apply the manifest and verify that the Deployment becomes healthy.