title: What can be the cause for helm error "TILLER: unexpected EOF"
body: <p>we execute in our automated pipelines this command:</p>
  
  <pre><code>helm list --namespace foobar
  </code></pre>
  
  <p>We experience rarely that error:</p>
  
  <pre><code>Error: Get https://172.21.0.1:443/api/v1/namespaces/kube-system/configmaps?labelSelector=OWNER%!D(MISSING)TILLER: unexpected EOF
  </code></pre>
  
  <p>The next run is working fine. in between we didn't change any thing.</p>
  
  <p>So we wonder, what the reason could be. Issue we found, which are more or less similar does not explain it, at least as far we understand them. As it seems to be a random error.</p>
  
  <p>We found these issues:</p>
  
  <ul>
  <li>helm still ignores kubeconfig #2520 - <a href="https://github.com/helm/helm/issues/2520" rel="nofollow noreferrer">https://github.com/helm/helm/issues/2520</a></li>
  <li>Error: Get <code>http://localhost:8080/api/v1/namespaces/kube-system/configmaps?labelSelector=OWNER%!D(MISSING)TILLER:</code> dial tcp 127.0.0.1:8080: connect: connection refused #4020 - <a href="https://github.com/helm/helm/issues/4020" rel="nofollow noreferrer">https://github.com/helm/helm/issues/4020</a></li>
  <li>Connection refused error when issuing helm install command #3460 - <a href="https://github.com/helm/helm/issues/3460" rel="nofollow noreferrer">https://github.com/helm/helm/issues/3460</a></li>
  <li>Helm list Error: Get <code>http://localhost:8080/api/v1/namespaces/kube-system/configmaps?labelSelector=OWNER%!D(MISSING)TILLER:</code> dial tcp 127.0.0.1:8080: connect: connection refused #3870 - <a href="https://github.com/helm/helm/issues/3870" rel="nofollow noreferrer">https://github.com/helm/helm/issues/3870</a></li>
  <li>Tiller pods can't connect to k8s apiserver #2464 - <a href="https://github.com/helm/helm/issues/2464" rel="nofollow noreferrer">https://github.com/helm/helm/issues/2464</a></li>
  </ul>