🚨 Action Required: Transition Away from gcr.io/kubebuilder/kube-rbac-proxy

[Camila Macedo]

Hi Everyone,

This is a reminder of an important change regarding the image gcr.io/kubebuilder/kube-rbac-proxy, which was historically used to secure metrics endpoints. 

🚨  This image will become unavailable, and ensuring that your projects no longer rely on it is crucial.
You must move as soon as possible, sometime in 2025, the GCR will go away.

Why Action Is Needed

If your project depends on this image, it may no longer work if you need to pull the image once it becomes unavailable.

What Do You Need to Do

If you want to continue using kube-rbac-proxy, you must replace the image and source it from another location.

👉 Note that kube-rbac-proxy has been discontinued in Kubebuilder and replaced by the  WithAuthenticationAndAuthorization feature available in Controller-Runtime.

This new approach provides equivalent protection without the need for the image. 

You can check the updated samples under the testdata directory. For reference, see: testdata/project-v4/cmd/main.go#L118-L135

To Support This Transition

We’ve created a discussion thread: https://github.com/kubernetes-sigs/kubebuilder/discussions/3907

• The thread is regularly updated with enhanced information, including details about new helper functions for protecting your metrics endpoint and guidance for transitioning from the image.
• A comprehensive FAQ section has been added to address common questions and offer step-by-step instructions.

We will continue to update this discussion with any new information or changes, so please stay tuned!

Cheers,

CAMILA MACEDO

SOFTWARE ENGINEER,

BLOG: www.dev4devs.com