<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>Most charts that follow the common chart development practices allow you to use an existing secret instead of creating one for you. This way, you can create your common secrets normally (without helm), and refer to them from the charts that need them, via a reference like <code>existingSecret</code> config key.</p>

<p>Take <a href="https://github.com/helm/charts/tree/6a8e70195b1a04a724269662a6700b4b76005062/stable/minio" rel="nofollow noreferrer">minio helm chart</a> for example: it accepts an <code>existingSecret</code> key as an alternative to passing an <code>accessKey</code> and a <code>secretKey</code>. </p>

<p>As you can see <a href="https://github.com/helm/charts/search?q=existingSecret&amp;unscoped_q=existingSecret" rel="nofollow noreferrer">in the main charts repo</a>, this is a pretty common practice.</p>
