I created EKS Kubernetes cluster with terraform. It all went fine, cluster is created and there is one EC2 machine on it. However, I can't init helm and install Tiller there. All the code is on https://github.com/amorfis/aws-eks-terraform

As stated in README.md, after cluster creation I update ~/.kube/config, create rbac, and try to init helm. However, it's pod is still pending:

gt; kubectl --namespace kube-system get pods
NAME                             READY   STATUS    RESTARTS   AGE
coredns-7554568866-8mnsm         0/1     Pending   0          3h
coredns-7554568866-mng65         0/1     Pending   0          3h
tiller-deploy-77c96688d7-87rb8   0/1     Pending   0          1h

As well as other 2 coredns pods.

What am i missing?

UPDATE: Output of describe:

gt; kubectl describe pod tiller-deploy-77c96688d7-87rb8 --namespace kube-system
Name:               tiller-deploy-77c96688d7-87rb8
Namespace:          kube-system
Priority:           0
PriorityClassName:  <none>
Node:               <none>
Labels:             app=helm
                    name=tiller
                    pod-template-hash=3375224483
Annotations:        <none>
Status:             Pending
IP:
Controlled By:      ReplicaSet/tiller-deploy-77c96688d7
Containers:
  tiller:
    Image:       gcr.io/kubernetes-helm/tiller:v2.12.2
    Ports:       44134/TCP, 44135/TCP
    Host Ports:  0/TCP, 0/TCP
    Liveness:    http-get http://:44135/liveness delay=1s timeout=1s period=10s #success=1 #failure=3
    Readiness:   http-get http://:44135/readiness delay=1s timeout=1s period=10s #success=1 #failure=3
    Environment:
      TILLER_NAMESPACE:    kube-system
      TILLER_HISTORY_MAX:  0
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from tiller-token-b9x6d (ro)
Conditions:
  Type           Status
  PodScheduled   False
Volumes:
  tiller-token-b9x6d:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  tiller-token-b9x6d
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:          <none>