<p>I have all sorts of problems with Kubernetes/helm, but I'm really new to it and so I'm not sure what I'm doing at all, despite spending a day trying to work it out.</p>

<p>I have a pod that's in a CrashLoopBackOff situation as I entered an incorrect port number in the Dockerfile. When I do a <code>kubectl -n dev get pods</code>, I can see it in the crash loop. I tried to kill it with <code>helm delete --purge emails</code> but I get the error <code>Error: unknown flag: --purge</code>. I tried to edit the chart with <code>kubectl edit pod emails -n dev</code>, but I get an error saying that the field cannot be changed.</p>

<p>But I can't delete the pod, so I'm not quite sure where to go from here. I've tried without the --purge flag and I get the error <code>Error: uninstall: Release not loaded: emails: release: not found</code>. I get the same if I try <code>helm uninstall emails</code> or pretty much anything.</p>

<p>To get to the crux of the matter, I believe it's because there's been an upgrade to the helm client to version v3.1.0 but the pods were created with v2.11.0. But I don't know how to roll back the client to this version. I've downloaded it via <code>curl -L https://git.io/get_helm.sh | bash -s -- --version v2.11.0</code> but I can't run <code>helm init</code> and so I'm still on v3.1.0</p>

<p>If I run <code>helm list</code>, I get an empty list. I have 16 running pods I can see through <code>kubectl -n dev get pods</code> but I don't seem to be able to do anything to any of them.</p>

<p>Is this likely to be because my helm client is the wrong version and, if so, how do I roll it back?</p>

<p>Thanks for any suggestions.</p>

EricP
<p>The problem is you mixed helm 2 and helm 3</p>

<p>The release was created by helm v2, so you need helm v2 to delete it, helm v3 won't be able to see releases created by helm v2.</p>

<p>You could do the following </p>

<blockquote>
  <ol>
  <li>download helm v2, delete release (I normally have both helm 2/3 in one folder, rename helm v2 to helm2). </li>
  <li>Optional, you can delete tiller, , as helm v3 won't need tiller anymore. just make sure no other release deployed by helm v2</li>
  <li>update your helm chart to use correct port</li>
  <li>use helm v3 deploy your updated chart</li>
  </ol>
</blockquote>
