<p>When I run <code>kubectl get secrets</code> after doing a <code>helm upgrade --install &lt;release-name&gt;</code> in Kubernetes cluster, our secrets got messy.</p>
<p>Is there any way to stop having <code>sh.helm.release.v1.</code> whenever I declare <code>kubectl get secrets</code>?</p>
<p><a href="https://i.stack.imgur.com/NQpku.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/NQpku.png" alt="enter image description here" /></a></p>

<p>No, these secrets are where Helm stores its state.</p>
<p>When you install or upgrade a release, Helm creates a new secret. The secret who’s name ends in <code>.airflow.v29</code> contains all the information Helm has about revision number <code>29</code> of the <code>airflow</code> release.</p>
<p>Whenever you run commands like <code>helm list</code>, <code>helm history</code>, or <code>helm upgrade</code>, Helm reads these secrets to know what it did in the past.</p>
<p>By default, Helm keeps up to 10 revisions in its state for each release, so up to 10 secrets per release in your namespace. You can have Helm keep a different number of revisions in its state with the <code>--history-max</code> flag.</p>
<p>If you don’t want to keep a history of changes made to your release, you can keep as little as a single revision in Helm’s state.</p>
<p>Running <code>helm upgrade --history-max=1</code> will keep the number of secrets Helm creates to a minimum.</p>
