We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Currently the manager deployment looks to reply upon the kubebuilder rbac proxy as per here and here
According to this issue the image will become unavailable on or after March 18, 2025 (due to the deprecation of gcr.io)
The simplest fix will be to migrate directly to the replacement for gcr.io/kubebuilder/kube-rbac-proxy which is called brancz/kube-rbac-proxy who's image is hosted on quay.io/brancz/kube-rbac-proxy.
Is this something you're aware of and already have in the backlog?
The text was updated successfully, but these errors were encountered:
Hi! We weren't aware, thank you for the heads up
Sorry, something went wrong.
No branches or pull requests
Currently the manager deployment looks to reply upon the kubebuilder rbac proxy as per here and here
According to this issue the image will become unavailable on or after March 18, 2025 (due to the deprecation of gcr.io)
The simplest fix will be to migrate directly to the replacement for gcr.io/kubebuilder/kube-rbac-proxy which is called brancz/kube-rbac-proxy who's image is hosted on quay.io/brancz/kube-rbac-proxy.
Is this something you're aware of and already have in the backlog?
The text was updated successfully, but these errors were encountered: