Security : run helm installs / upgrades / uninstalls as a service account local to the target namespace

未关闭
#688 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

@olevitt 已经在做这个了。

开始于 2026年10月23日。

  • #693 来自 @olevitt —— 未关闭

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
helm, java, kubernetes

调研方向

Start with the authenticationMode definition in Region.java and trace how Helm install, upgrade, and uninstall operations select credentials. Then inspect the onboarding flow that creates namespaces and their service accounts and role bindings. Done means a namespace-local service account mode is supported for sensitive Helm operations and onboarding provisions the required access; the issue leaves the mode name open for discussion.

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

描述

Currently, using the default mode (authenticationMode: serviceAccount, see https://github.com/InseeFrLab/onyxia-api/blob/2019ff5941a35989215e74216927a35fd69b2126/onyxia-model/src/main/java/fr/insee/onyxia/model/region/Region.java#L354), Onyxia executes helm installs / upgrades / uninstalls using it's own powerful service account.
This can be a security issue if the helm chart is compromised (or there is a flaw allowing injection).
We could add another mode, namespaceLocalServiceAccount (name to be discussed) that would execute sensitive helm operations (those that use user provided values) using a serviceaccount present in the target namespace.
Note that this would require the onboarding to create local serviceaccount (with corresponding rolebinding) in the namespace at the time of creation

主要语言
Java
星标
34
派生
34
平均合并
9 分钟
30 天内合并 PR
4

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

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

InseeFrLab/onyxia-api 的其他 Issue

查看 InseeFrLab/onyxia-api 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

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