⚠️ Action Required: Replace Deprecated gcr.io/kubebuilder/kube-rbac-proxy

[camilamacedo86]

Description

⚠️ The image gcr.io/kubebuilder/kube-rbac-proxy is deprecated and will become unavailable.
You must move as soon as possible, sometime from early 2025, the GCR will go away.

Unfortunately, we're unable to provide any guarantees regarding timelines or potential extensions at this time. Images provided under GRC will be unavailable from March 18, 2025, as per announcement. However, gcr.io/kubebuilder/may be unavailable before this date due to efforts to deprecate infrastructure.

• 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 take action as soon as possible.

• However, if your project is no longer using this image, no action is required, and you can close this issue.

Using the image gcr.io/kubebuilder/kube-rbac-proxy?

kube-rbac-proxy was historically used to protect the metrics endpoint. However, its usage has been discontinued in Kubebuilder. The default scaffold now leverages the WithAuthenticationAndAuthorization feature provided by Controller-Runtime.

This feature provides integrated support for securing metrics endpoints by embedding authentication (authn) and authorization (authz) mechanisms directly into the controller manager's metrics server, replacing the need for (https://github.com/brancz/kube-rbac-proxy) to secure metrics endpoints.

What To Do?

You must replace the deprecated image gcr.io/kubebuilder/kube-rbac-proxy with an alternative approach. For example:

• Update your project to use WithAuthenticationAndAuthorization:

  You can fully upgrade your project to use the latest scaffolds provided by the tool or manually make the necessary changes. Refer to the FAQ and Discussion for detailed instructions on how to manually update your project and test the changes.

• Alternatively, replace the image with another trusted source at your own risk, as its usage has been discontinued in Kubebuilder.

For further information, suggestions, and guidance:

• 📖 FAQ and Discussion
• 💬 Join the Slack channel: #kubebuilder.

NOTE: This issue was opened automatically as part of our efforts to identify projects that might be affected and to raise awareness about this change within the community. If your project is no longer using this image, feel free to close this issue.

We sincerely apologize for any inconvenience this may cause.

Thank you for your cooperation and understanding! 🙏

[erikgb]

Thanks @camilamacedo86! It seems kube-rbac-proxy is only referenced from the Enterprise install docs. This project is about to be transformed into a community project. Long-term plan is to fold the previous enterprise features into this project, and we will certainly review this issue when it's time for it.

CC @casibbald

[camilamacedo86]

HI @erikgb,

Thank you for checking this one. Just keep in mind that if your users are using this image, they can be affected when it goes away, so the best thing to do is to make sure that nobody is using it anymore.

[casibbald]

Hi, @camilamacedo86. Thanks for bumping this.

We will see if I can republish these images to ghcr.io/weaveworks/ over the next few weeks ahead of the decommissioning of gcr.io

As you may be aware, we are building a community around the Weaveworks Git Hub org and the tools previously built by the preeminent Weaveworks team before they took the very difficult decision of ceasing trading.

While building a team of community contributors, processes such as these take longer than expected due to our small but snowballing team of contributors.

We welcome new members with open hands, and should you wish to take this challenge on, we would happily have you on board our little team.

Best wishes