title: Initializing Tiller for Helm with Kubeadm - Kubernetes
body: <p>I'm using Kubeadm to create a cluster of 3 nodes</p>
  
  <ul>
  <li>One Master</li>
  <li>Two Workers</li>
  </ul>
  
  <p>I'm using weave as the network pod</p>
  
  <p>The status of my cluster is this:</p>
  
  <pre><code>NAME         STATUS   ROLES    AGE   VERSION
  darthvader   Ready    &lt;none&gt;   56m   v1.12.3
  jarjar       Ready    master   60m   v1.12.3
  palpatine    Ready    &lt;none&gt;   55m   v1.12.3
  </code></pre>
  
  <p>And I tried to init helm and tiller in my cluster</p>
  
  <blockquote>
    <p>helm init</p>
  </blockquote>
  
  <p>The result was this:</p>
  
  <pre><code>$HELM_HOME has been configured at /home/ubuntu/.helm.
  
  Tiller (the Helm server-side component) has been installed into your Kubernetes Cluster.
  
  Please note: by default, Tiller is deployed with an insecure 'allow unauthenticated users' policy.
  To prevent this, run `helm init` with the --tiller-tls-verify flag.
  For more information on securing your installation see: https://docs.helm.sh/using_helm/#securing-your-helm-installation
  Happy Helming!
  </code></pre>
  
  <p>And the status of my pods is this:</p>
  
  <pre><code>NAME                             READY   STATUS              RESTARTS   AGE
  coredns-576cbf47c7-8q6j7         1/1     Running             0          54m
  coredns-576cbf47c7-kkvd8         1/1     Running             0          54m
  etcd-jarjar                      1/1     Running             0          54m
  kube-apiserver-jarjar            1/1     Running             0          54m
  kube-controller-manager-jarjar   1/1     Running             0          53m
  kube-proxy-2lwgd                 1/1     Running             0          49m
  kube-proxy-jxwqq                 1/1     Running             0          54m
  kube-proxy-mv7vh                 1/1     Running             0          50m
  kube-scheduler-jarjar            1/1     Running             0          54m
  tiller-deploy-845cffcd48-bqnht   0/1     ContainerCreating   0          12m
  weave-net-5h5hw                  2/2     Running             0          51m
  weave-net-jv68s                  2/2     Running             0          50m
  weave-net-vsg2f                  2/2     Running             0          49m
  </code></pre>
  
  <p>The problem is that tiller is stuck in ContainerCreating State.</p>
  
  <p>And I ran</p>
  
  <blockquote>
    <p>kubectl describe pod tiller-deploy -n kube-system</p>
  </blockquote>
  
  <p>To check the status of tiller and I found The Next error:</p>
  
  <p><strong>Failed create pod sandbox: rpc error: code = DeadlineExceeded desc = context deadline exceeded</strong></p>
  
  <p><strong>Pod sandbox changed, it will be killed and re-created.</strong></p>
  
  <p>How I can to create the tiller deploy pod successfully? I don't understand why the <strong>pod sandbox</strong> is failing.</p>