<p>I have a problem where we essentially discovered a piece of stale configuration in a live environment on one of our deployments (a config map was added as a volume mount). Reading through the docs <a href="https://v3.helm.sh/docs/faq/changes_since_helm2/" rel="nofollow noreferrer">here</a> (search for 'Upgrades where live state has changed') we can see that helm v2 would purge changes that were introduced to a template via external actors. Whereas v3 is very clever and will merge externally introduced changes alongside template changes as long as they dont conflict.</p>
<p>So how do we in helm v3 run a upgrade that purges any manual template changes that may have been introduced?</p>

Ben Futterleib
<p>Based on the description, the <code>--force</code> flag should do the trick.</p>
<p><code>--force       force resource updates through a replacement strategy</code></p>
<p>However, there are some issues with it as mentioned in this <a href="https://github.com/helm/helm/issues/9433" rel="nofollow noreferrer">GitHub issue</a>.</p>
