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

Document namespace-scoped installs on the 1.x installation page

未关闭
  • 哪里不对？
#629 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

@boxcee-interview 已经在做这个了。

开始于 2026年10月21日。

  • #641 来自 @boxcee-interview —— 未关闭

评估

难度
3/5
预计耗时
1-2 天
新手友好度
54/100
Issue 类型
文档
描述清晰度
描述清楚
活跃度
活跃
技术栈
helm
领域
documentation

调研方向

Read docs-site/content/kagent/1.x/setup/installation.md and the global.watchNamespaces entry in 1.x/reference/helm.md; re-check behavior against the latest release tag and verify it on a cluster. Add the requested section after “Verify the installation,” with a values example, precedence guidance, and a link to the allowedNamespaces coverage in 1.x/reference/tools-ecosystem.md; done includes confirming reconciliation for watched and unwatched namespaces.

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

描述

help wanted

The 1.x installation page has no guidance on restricting kagent to specific namespaces. By default, the controller watches every namespace and the chart creates cluster-scoped RBAC. The only documentation of the alternative is the global.watchNamespaces row in 1.x/reference/helm.md. This issue replaces #97, which tracked the original multi-namespace change (kagent-dev/kagent#405).

Scope

Add an optional section, "Restrict kagent to specific namespaces", to docs-site/content/kagent/1.x/setup/installation.md. Place it after "Verify the installation" and before "Next steps". The section must show a global.watchNamespaces values example and explain the behavior below.

Verified behavior (chart at v1.0.0-alpha16, helm/kagent/templates/_helpers.tpl)

  • When global.watchNamespaces is empty (the default), the chart creates ClusterRoles and the controller watches all namespaces.
  • When global.watchNamespaces is set to a list, the chart creates a Role and RoleBinding in each listed namespace and limits the controller watch to the same list. The chart appends the install namespace automatically.
  • rbac.namespaces takes precedence over global.watchNamespaces whenever the key is present. An explicit rbac.namespaces: [] restores cluster-scoped RBAC. When rbac.namespaces is set, it must include the install namespace or the render fails.
  • config.kubernetes.watchNamespaces can narrow the watch below the RBAC scope. When it names a namespace outside rbac.namespaces, the render fails, because the controller would loop on Forbidden errors at runtime.
  • A RemoteMCPServer admits references from its own namespace only. Agents in other watched namespaces need allowedNamespaces on the tool server. Link to the existing coverage in 1.x/reference/tools-ecosystem.md rather than repeating it.

Before you start

  • Re-check the behavior above against the latest release tag. The precedence rules changed during the alpha series.
  • Test on a cluster. Install with two watched namespaces, create an Agent in each namespace and in one unwatched namespace, and confirm that the controller reconciles only the watched two.

Done when

  • The installation page has the section, with a values example and the precedence rules.
  • The section recommends global.watchNamespaces over the per-surface keys.
  • The section links to the allowedNamespaces coverage in tools-ecosystem.
  • The procedure has been run on a live cluster.
主要语言
TypeScript
星标
21
派生
69
平均合并
14 小时 16 分钟
30 天内合并 PR
105

环境准备

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

从这里开始

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

kagent-dev/website 的其他 Issue

查看 kagent-dev/website 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

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