<pre><code>helm install airflow . --namespace airflow -f my_values.yaml -f my_other_values.yaml
</code></pre>
<p>I executed the command from above but had to interrupt it, cannot re-execute it because gives me the error:</p>
<pre><code>Error: cannot re-use a name that is still in use
</code></pre>
<p>How can I fix it?</p>
<p>Thank you</p>

<p>Either <a href="https://docs.helm.sh/docs/helm/helm_uninstall/" rel="nofollow noreferrer"><code>helm uninstall</code></a> the existing release</p>
<pre class="lang-sh prettyprint-override"><code>helm uninstall airflow
helm install airflow . -n airflow -f values.dev.yaml ...
</code></pre>
<p>or use <a href="https://docs.helm.sh/docs/helm/helm_upgrade/" rel="nofollow noreferrer"><code>helm upgrade</code></a> to replace it with a new one</p>
<pre class="lang-sh prettyprint-override"><code>helm upgrade airflow . -n airflow -f values.dev.yaml ...
</code></pre>
<p>Both will have almost the same effect.  You can <a href="https://docs.helm.sh/docs/helm/helm_rollback/" rel="nofollow noreferrer"><code>helm rollback</code></a> the upgrade but the uninstall discards that history.</p>
<p>Mechanically, <code>helm install</code> and <code>helm upgrade</code> just send Kubernetes manifests to the cluster, and from there the cluster takes responsibility for actually doing the work.  Unless the chart has time-consuming hook jobs, it's actually possible that your current installation is fine and you don't need to do any of this (even if <code>helm install --wait</code> didn't report the Deployments were ready yet).</p>
<p>(The commands above assume you're using the current version 3 of Helm.  Helm 2 has slightly different syntax and commands, but at this point is unsupported and end-of-lifed.)</p>
