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

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

Abierto
  • ¿Algo no está bien?
#629 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
54/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
helm
Área
documentation

Línea de trabajo

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.

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

Descripción

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.
Lenguaje dominante
TypeScript
Estrellas
21
Forks
69
Merge medio
14 h 16 min
PR fusionados (30 d)
96

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

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 kagent-dev/website

Todos los issues de kagent-dev/website

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.