<p>I have a Kubernetes cluster running. All pods are running. This is a windows machine with minikube on it.</p>

<p>However <code>helm ls --debug</code> gives following error</p>

<pre><code>helm ls --debug
[debug] Created tunnel using local port: '57209'

[debug] SERVER: "127.0.0.1:57209"

Error: Get http://localhost:8080/api/v1/namespaces/kube-system/configmaps?labelSelector=OWNER%!D(MISSING)TILLER: dial tcp 127.0.0.1:8080: connect: connection refused
</code></pre>

<p>Cluster information</p>

<pre><code>kubectl.exe cluster-info
Kubernetes master is running at https://135.250.128.98:8443

To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.
</code></pre>

<p>kubectl service</p>

<pre><code>kubectl.exe get svc
NAME         TYPE        CLUSTER-IP   EXTERNAL-IP   PORT(S)   AGE
kubernetes   ClusterIP   10.96.0.1    &lt;none&gt;        443/TCP   3h
</code></pre>

<p>Dashboard is accessible at <code>http://135.250.128.98:30000</code></p>

<p>kube configuration:</p>

<pre><code>apiVersion: v1
clusters:
- cluster:
    certificate-authority: C:\Users\abc\.minikube\ca.crt
    server: https://135.250.128.98:8443
  name: minikube
contexts:
- context:
    cluster: minikube
    user: minikube
  name: minikube
current-context: minikube
kind: Config
preferences: {}
users:
- name: minikube
  user:
    as-user-extra: {}
    client-certificate: C:\Users\abc\.minikube\client.crt
    client-key: C:\Users\abc\.minikube\client.key
</code></pre>

<p>Is there a solution? Most online resource says cluster is misconfigured. But not sure what is misconfigured and how to solve this error?</p>

Dheeraj Joshi
<p>What worked for me when I was facing the same issue was changing <code>automountServiceAccountToken</code> to <code>true</code>.</p>

<p>Use the following command to edit the tiller-deploy</p>

<pre><code>kubectl --namespace=kube-system edit deployment/tiller-deploy
</code></pre>

<p>And change <code>automountServiceAccountToken</code> to <code>true</code></p>
