<p>it might be simple question but can't find anywhere if it's duable;</p>

<p>Is it possible to have values files for helm charts (stable/jenkins let's say) and have two different values files for it?</p>

<p>I would like in values_a.yaml have some values like these:</p>

<pre><code>master:
  componentName: "jenkins-master"
  image: "jenkins/jenkins"
  tag: "lts"
...
  password: {{ .Values.secrets.masterPassword }}
</code></pre>

<p>and in the values_b.yaml - which will be encrypted with AWS KMS</p>

<pre><code>secrets:
  masterPassword: xxx
</code></pre>

<p>the above code doesn't work and wanted to know, as you can put those vars in kube manifests like it </p>

<pre><code>apiVersion: v1
kind: ConfigMap
metadata:
  name: {{ .Values.config.name }}
  namespace: {{ .Values.config.namespace }}
...

</code></pre>

<p>can they be somehow passed to other values files</p>

<hr>

<p>EDIT:</p>

<p>If it was possible I would just put the </p>

<pre><code>master:
  password: xxx
</code></pre>

<p>in values_b.yaml but vars cannot be duplicated, and the official helm chart expects the <code>master.password</code> val from that file - so has to somehow pass it there but in encrypted way</p>

potatopotato
<p>I'm not quite sure but this feature of <code>helm</code> might help you.</p>

<blockquote>
  <p>Helm gives you the functionality to pass custom <code>Values.yaml</code> which have higher precedence over the fields of the main <code>Values.yaml</code> while performing <code>helm install</code> or <code>helm upgrade</code>.</p>
</blockquote>

<h3>For Helm 3</h3>

<pre class="lang-sh prettyprint-override"><code>$ helm install &lt;name&gt; ./mychart -f myValues.yaml
</code></pre>

<h3>For Helm 2</h3>

<pre class="lang-sh prettyprint-override"><code>$ helm install --name &lt;name&gt; ./mychart --values myValues.yaml
</code></pre>
