<p>I installed a chart on a K8s cluster using helm3. Later I context switched to another Kubernetes cluster, did a few things, and then switched back on the original cluster in which I deployed the chart. I find that <code>helm list</code> is not listing any releases (which is very strange). However, I find that the secret in which helm stores release info still exists in the current namespace.</p>
<pre class="lang-sh prettyprint-override"><code>sh.helm.release.v1.my-chart.v1   helm.sh/release.v1                    1      66m
</code></pre>
<p>Is there a way to recover the release information for the helm client from the secret, given that all the info about releases is stored in the secret?</p>
<p>I'm using the following version:</p>
<pre class="lang-sh prettyprint-override"><code>version.BuildInfo{Version:&quot;v3.1.2&quot;, GitCommit:&quot;d878d4d45863e42fd5cff6743294a11d28a9abce&quot;, GitTreeState:&quot;clean&quot;, GoVersion:&quot;go1.13.8&quot;}
</code></pre>

quantdaddy
<blockquote>
<p>then switched back on the original cluster in which I deployed the chart. I find that helm list is not listing any releases (which is very strange)</p>
</blockquote>
<p>That's indeed very strange 🤔.</p>
<blockquote>
<p><code>sh.helm.release.v1.my-chart.v1   helm.sh/release.v1                    1      66m</code></p>
</blockquote>
<p>This is all Helm should need to find your release. You can inspect it 🔎 if it's corrupted.</p>
<pre class="lang-sh prettyprint-override"><code>$ kubectl get secret sh.helm.release.v1.mychart.v1 -o=json | jq '.data.release' | tr -d '&quot;' | base64 -d | base64 -d &gt; myrelease.gz
$ gunzip myrelease.gz
$ cat myrelease
</code></pre>
<p>You can also run <code>helm ls</code> on all namespaces, to double-check that you are not missing the release in a different namespace.</p>
<pre class="lang-sh prettyprint-override"><code>$ helm ls -A
</code></pre>
<p>✌️</p>
