title: No nodes available in AWS EKS
body: <p>I am trying to setup an AWS EKS cluster and followed the instructions in <a href="https://docs.aws.amazon.com/eks/latest/userguide/getting-started.html" rel="nofollow noreferrer">https://docs.aws.amazon.com/eks/latest/userguide/getting-started.html</a>. But  while trying to setup the dashboard I realized I do not have any nodes and don't know why.</p>
  
  <p>Yes, I made sure that the CloudFormation stack for my nodes has the exact name of my EKS cluster and I applied the <code>aws-auth-cm.yaml</code> with the stacks <code>NodeInstanceRole</code>.</p>
  
  <p>A similar question came up here <a href="https://stackoverflow.com/questions/52542933/amazon-kubernetes-aws-eks-is-not-getting-created-properly-or-not-synched-with-ku">Amazon Kubernetes AWS-EKS is not getting created properly or not synched with kubectl</a> but there is no usable information there.</p>
  
  <p>Here is some info:</p>
  
  <pre><code>$ kubectl get svc
  NAME         TYPE        CLUSTER-IP   EXTERNAL-IP   PORT(S)   AGE
  kubernetes   ClusterIP   &lt;IP&gt;         &lt;none&gt;        443/TCP   11d
  
  $ kubectl get all --namespace=default
  NAME                 TYPE        CLUSTER-IP   EXTERNAL-IP   PORT(S)   AGE
  service/kubernetes   ClusterIP   &lt;IP&gt;         &lt;none&gt;        443/TCP   11d
  
  $ kubectl get nodes --namespace=kube-system
  No resources found.
  </code></pre>
  
  <p><code>get nodes</code> gives <code>No resources found</code> for any of the namespaces I have: <code>kube-system</code>, <code>kube-public</code>, or <code>default</code>.</p>
  
  <pre><code>$ kubectl get all --namespace=kube-system
  NAME                                        READY     STATUS    RESTARTS   AGE
  pod/heapster-7ff8d6bf9f-qv56t               0/1       Pending   0          44m
  pod/kube-dns-69ff9fcd66-ls9w7               0/3       Pending   0          11d
  pod/kubernetes-dashboard-669f9bbd46-xthpq   0/1       Pending   0          45m
  pod/monitoring-influxdb-cc95575b9-qjk4r     0/1       Pending   0          44m
  
  NAME                           TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)         AGE
  service/heapster               ClusterIP   &lt;IP&gt;             &lt;none&gt;        80/TCP          44m
  service/kube-dns               ClusterIP   &lt;IP&gt;             &lt;none&gt;        53/UDP,53/TCP   11d
  service/kubernetes-dashboard   ClusterIP   &lt;IP&gt;             &lt;none&gt;        443/TCP         45m
  service/monitoring-influxdb    ClusterIP   &lt;IP&gt;             &lt;none&gt;        8086/TCP        44m
  
  NAME                                            DESIRED   CURRENT   READY     UP-TO-DATE   AVAILABLE   NODE SELECTOR   AGE
  daemonset.apps/aws-node                         0         0         0         0            0           &lt;none&gt;          11d
  daemonset.apps/kube-proxy                       0         0         0         0            0           &lt;none&gt;          11d
  daemonset.apps/nvidia-device-plugin-daemonset   0         0         0         0            0           &lt;none&gt;          34m
  
  NAME                                   DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
  deployment.apps/heapster               1         1         1            0           44m
  deployment.apps/kube-dns               1         1         1            0           11d
  deployment.apps/kubernetes-dashboard   1         1         1            0           45m
  deployment.apps/monitoring-influxdb    1         1         1            0           44m
  
  NAME                                              DESIRED   CURRENT   READY     AGE
  replicaset.apps/heapster-7ff8d6bf9f               1         1         0         44m
  replicaset.apps/kube-dns-69ff9fcd66               1         1         0         11d
  replicaset.apps/kubernetes-dashboard-669f9bbd46   1         1         0         45m
  replicaset.apps/monitoring-influxdb-cc95575b9     1         1         0         44m
  </code></pre>
  
  <p>UPDATE:</p>
  
  <p>After I send a Kubernetes API call from my backend to launch some pods I get the following output (<code>kubectl get jobs</code> is similar) but still no actual instances spin up and the jobs never execute.</p>
  
  <pre><code>$ kubectl get svc
  kubernetes                                      ClusterIP   &lt;IP&gt;     &lt;none&gt;        443/TCP                                                       14d
  svc-3d1de3dc-7ca1-1f83-7a5e-548e5c5b4d12        NodePort    &lt;IP&gt;     &lt;none&gt;        8082:32433/TCP,8081:30374/TCP,8096:31178/TCP,8083:31067/TCP   1m
  svc-3d1de3dc-7ca1-1f83-7a5e-548e5c5b4d12-sut0   ClusterIP   &lt;IP&gt;     &lt;none&gt;        50001/TCP                                                     1m
  svc-7429ae6b-6f4b-012b-2d93-7c244109090b        NodePort    &lt;IP&gt;     &lt;none&gt;        8082:30736/TCP,8081:31272/TCP,8096:30857/TCP,8083:30949/TCP   1m
  svc-7429ae6b-6f4b-012b-2d93-7c244109090b-sut0   ClusterIP   &lt;IP&gt;     &lt;none&gt;        50001/TCP                                                     1m
  svc-89e81309-f6e4-21b1-ab8d-ecfb74d08010        NodePort    &lt;IP&gt;     &lt;none&gt;        8082:32072/TCP,8081:31236/TCP,8096:30000/TCP,8083:31257/TCP   1m
  svc-89e81309-f6e4-21b1-ab8d-ecfb74d08010-sut0   ClusterIP   &lt;IP&gt;     &lt;none&gt;        50001/TCP                                                     1m
  svc-c196e61f-098e-7b10-9d05-6d06ccbdbb9f        NodePort    &lt;IP&gt;     &lt;none&gt;        8082:32541/TCP,8081:30305/TCP,8096:31738/TCP,8083:31846/TCP   1m
  svc-c196e61f-098e-7b10-9d05-6d06ccbdbb9f-sut0   ClusterIP   &lt;IP&gt;     &lt;none&gt;        50001/TCP                                                     1m
  </code></pre>