<p>I have some Helm value files.</p>
<p>There are <code>value.yaml</code>, <code>value.dev.yaml</code>, <code>value.test.yaml</code>, ... file.</p>
<p>In <code>value.dev.yaml</code>:</p>
<pre><code>env:
  &quot;Environment&quot;  &quot;development&quot;
</code></pre>
<p>For some parameters in <code>value.yaml</code> file, I expected they override or insert them into pod parameters while deployment.</p>
<p>If I set up them into each <code>value.dev.yaml</code>, <code>value.test.yaml</code>,... it works with <code>helm upgrade --install --set env.parameter=$variable</code></p>
<p>Now I want to define all variables in <code>value.yaml</code> file and expect them insert (override) them in to pods while deployment.</p>
<p>In <code>value.yaml</code> file :</p>
<pre><code>env:
  &quot;Appconfig&quot;: &quot;dev&quot;
</code></pre>
<p>I'd like to combine them while deployment:</p>
<pre><code>env:
  &quot;Environment&quot;: &quot;development&quot;
  &quot;Appconfig&quot;: &quot;dev&quot;
</code></pre>
<p>Apreciate your help !</p>

Thanh Nguyen Van
<p>You can specify the <code>--values</code>/<code>-f</code> flag multiple times. The priority will be given to the <strong>last</strong> (right-most) file specified. For example, if both <code>myvalues.yaml</code> and <code>override.yaml</code> contained a key called 'Test', the value set in <code>override.yaml</code> would take precedence:</p>
<pre><code>$ helm install -f myvalues.yaml -f override.yaml  myredis ./redis
</code></pre>
<ul>
<li>Ref <a href="https://helm.sh/docs/helm/helm_install/" rel="nofollow noreferrer">Helm Install Doc</a></li>
</ul>
