Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
  • ¿Algo no está bien?
#286 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
42/100
Tipo de issue
Refactorización
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
docker, kubernetes
Área
devops, infrastructure

Línea de trabajo

Busca en el repositorio la referencia exacta de imagen gcr.io/kubebuilder/kube-rbac-proxy para confirmar si todavía se utiliza. Lee la documentación de WithAuthenticationAndAuthorization y la FAQ o la guía de migración enlazada antes de elegir el camino de migración. Se considera completado cuando la imagen obsoleta ya no es necesaria y el endpoint de métricas sigue protegido.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

This issue was raised because we found the imagegcr.io/kubebuilder/kube-rbac-proxyin the files of this repository.

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 is using gcr.io/kubebuilder/kube-rbac-proxy, it may fail to work when the image can no longer be pulled. If not, nothing 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 scaffolding provided by the upstream versions of Operator-SDK or Kubebuilder tools or manually make the necessary changes. Refer to the FAQ and Discussion or migration guide 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.

💡 The section How can I manually change my project to switch to Controller-Runtime's built-in auth protection? at FAQ provides guidance on how to manually update your projects and test it out.

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! 🙏

Lenguaje dominante
Go
Estrellas
23
Forks
24
Merge medio
1 d 23 h
PR fusionados (30 d)
1

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Azure/aks-engine-azurestack

Todos los issues de Azure/aks-engine-azurestack

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.