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 move as soon as possible, sometime from early 2025, the GCR will go away.
The usage of the project kube-rbac-proxy was discontinued from Kubebuilder and Operator-SDK. It was replaced for similar protection using authn/authz via Controller-Runtime's feature WithAuthenticationAndAuthorization.
👉 For more information and guidance see the discussion kubernetes-sigs/kubebuilder#3907
Here's the usage in kubeflow/kubeflow/components/notebook-controller:
https://github.com/kubeflow/kubeflow/blob/4275d99754ac91f6cf5654b03824a73825e9fe55/components/notebook-controller/config/default/manager_auth_proxy_patch.yaml#L1-L25