title: Setting up SSL between Helm and Tiller
body: <p>I am following these instructions to setup SSL between helm and tiller
  When I <code>helm-init</code> like this, I get an error</p>
  
  <pre><code>helm init --tiller-tls --tiller-tls-cert ./tiller.cert.pem --tiller-tls-key ./tiller.key.pem --tiller-tls-verify --tls-ca-cert ca.cert.pem
  $HELM_HOME has been configured at /Users/Koustubh/.helm.
  Warning: Tiller is already installed in the cluster.
  (Use --client-only to suppress this message, or --upgrade to upgrade Tiller to the current version.)
  Happy Helming!
  </code></pre>
  
  <p>When I check my pods, I get </p>
  
  <pre><code>tiller-deploy-6444c7d5bb-chfxw                       0/1       ContainerCreating   0          2h
  </code></pre>
  
  <p>and after describing the pod, I get</p>
  
  <pre><code>Warning  FailedMount  7m (x73 over 2h)  kubelet, gke-myservice-default-pool-0198f291-nrl2  Unable to mount volumes for pod "tiller-deploy-6444c7d5bb-chfxw_kube-system(3ebae1df-e790-11e8-98ae-42010a9800f9)": timeout expired waiting for volumes to attach or mount for pod "kube-system"/"tiller-deploy-6444c7d5bb-chfxw". list of unmounted volumes=[tiller-certs]. list of unattached volumes=[tiller-certs default-token-9x886]
    Warning  FailedMount  1m (x92 over 2h)  kubelet, gke-myservice-default-pool-0198f291-nrl2  MountVolume.SetUp failed for volume "tiller-certs" : secrets "tiller-secret" not found
  </code></pre>
  
  <p>If I try to delete the running <code>tiller</code> pod like this, it just gets stuck
   <code>
   helm reset --debug --force
  </code></p>
  
  <p>How can I solve this issue? <code>--upgrade flag</code> with <code>helm init</code>, but that doesn't work either.</p>