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

[Feature]: Allow external RBAC configuration/dropping bootstrap-only RBAC permissions

Abierto
  • ¿Algo no está bien?
#3,035 1 comentario 2 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
go, kubernetes
Área
devops

Línea de trabajo

The payload names no files or tests, so the first step is locating where the operator creates its own RBAC objects at startup in the Go code. The issue asks for an opt-out toggle or env var, but the maintainers have not replied yet and the design is undecided, so agree on the approach in the thread before writing code. Done means RBAC management can be skipped without the operator crashing when it lacks permissions.

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

Descripción

feature lifecycle/frozen needs-triage

👋🏻
We've been looking at using gpu-operator to simplify some of our GPU infrastructure (and get rid of a couple of pain points at the same time!) - however, and, this might just be an us-problem: at $DAYJOB, we prefer to manage RBAC configurations ourselves/explicitly (i.e., have our own manifests in our gitops repo).

We looked into having our own ClusterRole/ClusterRoleBindings created and dropping any permissions that were unnecessary in our infra (or too broad and not required if the operator no longer needed them to bootstrap itself), but the operator currently doesn't expose a way to skip trying to manage its RBAC configs.
(i.e., we tried to do this, and were blocked by the operator crashing when it unconditionally tried to manage RBAC and whatnot on launch without the necessary permissions to do so :p)

As far as I can tell, there's no way to skip this code atm, so I'm totally happy to give implementing a feature toggle/env var/whatever a shot as long as y'all don't think this isn't a silly idea...but I figured y'all would want an issue/feature request first before talking about PRs/implementation :D

Lenguaje dominante
Go
Estrellas
2.9k
Forks
569
Merge medio
23 h 33 min
PR fusionados (30 d)
85

Preparar el entorno

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 NVIDIA/gpu-operator

Todos los issues de NVIDIA/gpu-operator

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.