Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

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

Open
  • Is something wrong?
#3,035 0 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
go, kubernetes
Domain
devops

Research direction

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.

Written by the indexing model from the issue text.

Description

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

Dominant language
Go
Stars
2.9k
Forks
569
Avg merge
1d 7h
Merged PRs (30d)
76

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from NVIDIA/gpu-operator

All issues in NVIDIA/gpu-operator

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.