Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

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

已关闭
#3,035 4 条评论 2 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
25/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
go, kubernetes
领域
devops

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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

主要语言
Go
星标
2.9k
派生
582
平均合并
2 天 1 小时
30 天内合并 PR
61

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

NVIDIA/gpu-operator 的其他 Issue

查看 NVIDIA/gpu-operator 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。