One kubeseal instance to manage secrets in a subset of namespaces
#335 geöffnet am 13.12.2019
Repository-Metriken
- Stars
- (9.222 Sterne)
- PR-Merge-Metriken
- (PR-Metriken ausstehend)
Beschreibung
Hello,
I'm looking for a solution like kubeseal to encrypt/decrypt on the fly our kubernetes secrets to allow us to put all of them into a git repository (helm chart).
So I followed the recent Improvements made on the tool like the ability to deploy kubeseal into a single namespace and to configure it to not watch secrets in all namespace (flag: --all-namespaces=false).
Now my question is:
We are sharing a kubernetes cluster (we are restricted in namespaces that we owned, no admin access on the cluster) and we have applications in different namespaces. Can we have a kubeseal instance deployed on a dedicated namespace and tell him to manage encryption/decryption of secrets located in different namespaces (not all namespaces but a list of allowed namespaces) or Do I need to deploy a kubeseal controller on each namespace and switch between all of them when I want to encrypt a secret (because I think not the same encryption key pair is used)?
Thanks you for your reply