<p>I was also encountering the error message when running <code>helm version</code> or <code>helm list</code></p>

<pre><code>kubectl port-forward -n kube-system tiller-deploy-xxxxxxxxxxxxxxx 44134
error: error upgrading connection: error dialing backend: No SSH tunnels currently open. Were the targets able to accept an ssh-key for user "gke-xxxxxxxxxxx"?
</code></pre>

<p>The root issue appears to be related to the GKE port-forwarding. is the ssh key configurable anywhere? I can see this key being added to my metadata, but it is not part of the metadata for the GKE nodes. </p>

turnupthechill
<p>Issue could be related to <a href="https://v2.helm.sh/docs/using_helm/" rel="nofollow noreferrer">certicates</a>. Please check part on</p>

<pre><code>Q: On GKE (Google Container Engine) I get “No SSH tunnels currently open”
</code></pre>
