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

Ouverte
#780 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
15/100
Type d'issue
Fonctionnalité
Clarté
À clarifier
Activité
Active
Stack technique
helm, kubernetes
Domaine
devops, security

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
Python
Étoiles
3.5k
Forks
328
Merge moyen
16 h 25 min
PR mergées (30 j)
121

Préparer son environnement

Ce projet ne fournit ni conteneur de développement, ni Dockerfile, ni guide de contribution : l'installation est à votre charge. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de superlinked/sie

Toutes les issues de superlinked/sie

Issues similaires

Plus d'issues Python

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.