What/Why

What are you proposing?

Change kube-rbac-proxy for any alternative fork or start using WithAuthenticationAndAuthorization

What problems are you trying to solve?

Soon the docker image will be unavailable in repository, maybe alternativ will be still on DockerHUb

Are there any security considerations?

Yes the Rbac proxy using very old version of GO language and has many CVE and lots companies started blocking operator deployment in envrimoments

Are there any breaking changes to the API

Possible yes

What is the user experience going to be?

Better deployment, no future problems about deploying operator

IMPORTANT NOTICE its on kubeBuilder repo:
https://github.com/kubernetes-sigs/kubebuilder

⚠️ IMPORTANT NOTICE: Images under gcr.io/kubebuilder/ Will Be Unavailable Soon

If your project uses gcr.io/kubebuilder/kube-rbac-proxy it will be affected. Your project may fail to work if the image cannot be pulled. You must move as soon as possible, sometime from early 2025, the GCR will go away.

The usage of the project kube-rbac-proxy was discontinued from Kubebuilder and replaced for similar protection using authn/authz via Controller-Runtime's feature WithAuthenticationAndAuthorization.

For more information and guidance see the discussion kubernetes-sigs/kubebuilder#3907

Alternativ

https://github.com/brancz/kube-rbac-proxy