🚨 Action Required: Ensure that you no longer use gcr.io/kubebuilder/kube-rbac-proxy images #5339
camilamacedo86
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
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! 🙏
Beta Was this translation helpful? Give feedback.
All reactions