design(helm): define separation for operator-supplied dependency credentials

Abierto
#780 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
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
15/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
helm, kubernetes
Área
devops, security

Línea de trabajo

Start with #767's pinned dependency credential inventory and the Helm chart templates/values for Grafana, KEDA, Prometheus/Alertmanager, Loki and MinIO named in the issue. The deliverable is a reviewed design covering operator-declared key inventories versus bounded whole-Secret separation, namespace and activation semantics, and SIE worker/gateway/MCP/upstream consumers; no default chart change or live upgrade is expected.

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

Descripción

Follow-up to #767's pinned dependency credential inventory. The known first-class Secret/key refs can use the shared Helm inventory. Operator-supplied configuration has no reliable fixed key layout, so it remains outside that automatic guarantee. This issue records those siblings explicitly; it does not imply an unauthenticated way to change Helm values.

Assessed surfaces:

  • Grafana envValueFrom, envFromSecret/envFromSecrets, extra env/volumes and raw configuration. Explicit env entries can duplicate names; envFrom does not replace explicit env values. No assumption that one static inventory enumerates arbitrary injected credentials.
  • KEDA grpcTLSCertsSecret and hashiCorpVaultTLS: literal whole-Secret mounts without items in the pinned operator and metrics Pods. The chart provides no fixed filenames. Existing external certificate Issuers also hide their backing Secret behind another resource. The structured KEDA serving and generated CA Issuer refs are handled in #767.
  • Prometheus/Alertmanager Secret lists, arbitrary provider configs, externally managed Issuers/certificates and additional CA settings.
  • Loki enterprise/GEL and cloud-storage/raw configuration; MinIO extra Secrets and external TLS/provider configuration. The normal NGINX gateway .htpasswd and MinIO rootUser/rootPassword refs are handled in #767.
  • Custom dependency binaries can change which key a controller reads; a chart inventory cannot prove their executable contract.

Future work needs a reviewed design: decide whether operator-declared key inventories or bounded whole-Secret separation are appropriate, define namespace and activation semantics, and cover all SIE worker/gateway/MCP/upstream consumers with real-render and mutation controls. Do not silently turn a finite key inventory into a claim of universal credential isolation. No default change or live cluster upgrade is requested here.

Lenguaje dominante
Python
Estrellas
3.5k
Forks
328
Merge medio
16 h 25 min
PR fusionados (30 d)
121

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 superlinked/sie

Todos los issues de superlinked/sie

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.