<p>I have a couple Charts which all need access to the same Kubernetes Secret. My initial plan was to create a Chart just for those Secrets but it seems <a href="https://github.com/helm/helm/issues/4670" rel="nofollow noreferrer">Helm doesn't like that</a>. I am thinking this must be a common problem and am wondering what folks generally do to solve this problem?</p>

<p>Thanks!</p>

adelbertc
<p>Best practice is, don't save any sensitive secrets in kubernetes clusters. kubernetes secret is <strong>encode</strong>, not <strong>encrypt</strong>. </p>

<p>You can reference the secret via aws ssm/secrets manager, hashicorp Vault or other similars. </p>

<p><a href="https://github.com/aws-samples/aws-workshop-for-kubernetes/tree/master/04-path-security-and-networking/401-configmaps-and-secrets" rel="nofollow noreferrer">https://github.com/aws-samples/aws-workshop-for-kubernetes/tree/master/04-path-security-and-networking/401-configmaps-and-secrets</a></p>
