<p>I have a question about a Helm upgrade. I'm working on a chart foo-1.0.0 which deploys a pod with a docker image bar:4.5.1.</p>

<p>I have a release "myrelease" based on this chart foo in version 1.0.0 (with a bar:4.5.1 running inside).</p>

<p>Now, I make a fix on bar, rebuild the image <strong>bar:4.5.2</strong>, change the image in the chart but I did not bump its version. It is still foo-1.0.0</p>

<p>I launch:</p>

<pre><code>$ helm upgrade myrelease repo/foo --version 1.0.0
</code></pre>

<p>My problem is that after the upgrade, my pod is still running the bar:4.5.1 instead the 4.5.2</p>

<p>Is the a "cache" in tiller? It seems that tiller did not download foo-1.0.0 again. Is there a way to force it to download?</p>

<p>You need to change the <code>tag</code> version in the image section of  <code>values.yaml</code>:</p>
<pre><code>image:
  repository: bar
  tag: 4.5.2
  pullPolicy: Always
</code></pre>
<p>and then run the following command:</p>
<pre><code>helm upgrade myrelease repo/foo 
</code></pre>
<p>or just run the following:</p>
<pre><code>helm upgrade myrelease repo/foo --set=image.tag=1.2.2
</code></pre>
<p>and set the applicable image version.</p>
