You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
⚠️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?
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:
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:
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! 🙏
The text was updated successfully, but these errors were encountered:
@sunya-ch Since kube-rbac-proxy is only used in cpe-operator which is being deprecated should we continue to support it with some alternative or are we good to remove it?
Description
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.
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:WithAuthenticationAndAuthorization
:For further information, suggestions, and guidance:
We sincerely apologize for any inconvenience this may cause.
Thank you for your cooperation and understanding! 🙏
The text was updated successfully, but these errors were encountered: