<p>Following this document step by step:</p>

<p><a href="https://docs.aws.amazon.com/eks/latest/userguide/getting-started.html?shortFooter=true" rel="nofollow noreferrer">https://docs.aws.amazon.com/eks/latest/userguide/getting-started.html?shortFooter=true</a></p>

<p>I created EKS cluster using aws cli instead-of UI. So I got the following output</p>

<pre><code>proxy-kube$ kubectl get svc 
NAME         TYPE        CLUSTER-IP   EXTERNAL-IP   PORT(S)   AGE
kubernetes   ClusterIP   10.100.0.1   &lt;none&gt;        443/TCP   18h
</code></pre>

<p>But when I am following this getting started and associating Worker nodes with the cluster, I get </p>

<pre><code>proxy-kube$ kubectl get nodes 
No resources found.
</code></pre>

<p>I can see 3 EC2 instances created and running in AWS console (UI).
But I am unable to deploy and run even Guestbook application. 
When I deploy application, I get following: </p>

<pre><code>~$ kubectl get services -o wide
NAME           TYPE           CLUSTER-IP       EXTERNAL-IP                                                               PORT(S)          AGE       SELECTOR
guestbook      LoadBalancer   10.100.46.244    a08e89122c10311e88fdd0e3fbea8df8-1146802048.us-east-1.elb.amazonaws.com   3000:32758/TCP   17s       app=guestbook
kubernetes     ClusterIP      10.100.0.1       &lt;none&gt;                                                                    443/TCP          21h       &lt;none&gt;
redis-master   ClusterIP      10.100.208.141   &lt;none&gt;                                                                    6379/TCP         1m        app=redis,role=master
redis-slave    ClusterIP      10.100.226.147   &lt;none&gt;
</code></pre>

<p>But if I try to access EXTERNAL-IP, It shows </p>

<blockquote>
  <p>server is not reachable</p>
</blockquote>

<p>in browser.</p>

<p>Also tried to get Dashboard for kubernetes but it failed to show anything on 127.0.0.1:8001</p>

<p>Does anyone know what might be going wrong? 
Any help on this is appreciated. </p>

<p>Thanks</p>

shraddha
<p>Looks you your kubelet (your node) is not registering with the master. If you don't have any nodes basically you can't run anything.</p>

<p>You can ssh into one of the nodes and check the logs in the kubelet with something like this:</p>

<pre><code>journalctl -xeu kubelet
</code></pre>

<p>Also, it would help to post the output of <code>kubectl describe deployment &lt;deployment-name&gt;</code> and <code>kubectl get pods</code></p>
