title: Why tiller connect to localhost 8080 for kubernetes api?
body: <p>When use helm for kubernetes package management, after installed the helm client,</p>
  
  <p>after</p>
  
  <pre><code>helm init
  </code></pre>
  
  <p>I can see tiller pods are running on kubernetes cluster, and then when I run <code>helm ls</code>, it gives an error: </p>
  
  <pre><code>Error: Get http://localhost:8080/api/v1/namespaces/kube-system/configmaps?labe 
  lSelector=OWNER%3DTILLER: dial tcp 127.0.0.1:8080: getsockopt: connection 
  refused
  </code></pre>
  
  <p>and use <code>kubectl logs</code> I can see similar message like:</p>
  
  <pre><code>[storage/driver] 2017/08/28 08:08:48 list: failed to list: Get 
  http://localhost:8080/api/v1/namespaces/kube-system/configmaps?
  labelSelector=OWNER%3DTILLER: dial tcp 127.0.0.1:8080: getsockopt: connection 
  refused
  </code></pre>
  
  <p>I can see the tiller pod is running at one of the node instead of master, there is no api server running on that node, why it connects to 127.0.0.1 instead of my master ip?</p>