<p>Github repo: <a href="https://github.com/oussamabouchikhi/udagram-microservices" rel="nofollow noreferrer">https://github.com/oussamabouchikhi/udagram-microservices</a></p>
<p>After I configured the kubectl with the AWS EKS cluster, I deployed the services using these commands</p>
<pre><code>kubectl apply -f env-configmap.yaml
kubectl apply -f env-secret.yaml
kubectl apply -f aws-secret.yaml
# this is repeated for all services 
kubectl apply -f svcname-deploymant.yaml
kubectl apply -f svcname-service.yaml
</code></pre>
<p><a href="https://i.stack.imgur.com/Qpe14.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/Qpe14.png" alt="enter image description here" /></a></p>
<p>But the pods took hours and still in PENDING state, and when I run the command <code>kubectl describe pod &lt;POD_NAME&gt;</code> I get the follwing info</p>
<p>reverseproxy-667b78569b-2c6hv pod: <a href="https://pastebin.com/3xF04SEx" rel="nofollow noreferrer">https://pastebin.com/3xF04SEx</a> <br/>
udagram-api-feed-856bbc5c45-jcgtk pod: <a href="https://pastebin.com/5UqB79tU" rel="nofollow noreferrer">https://pastebin.com/5UqB79tU</a> <br/>
udagram-api-users-6fbd5cbf4f-qbmdd pod: <a href="https://pastebin.com/Hiqe1LAM" rel="nofollow noreferrer">https://pastebin.com/Hiqe1LAM</a></p>

Oussama Bouchikhi
<p>From your <code>kubectl describe pod &lt;podname&gt;</code></p>
<blockquote>
<p>Warning  FailedScheduling  2m19s (x136 over 158m)  default-scheduler  0/2 nodes are available: 2 Too many pods.</p>
</blockquote>
<p>When you see this, it means that your nodes in AWS EKS is full.</p>
<p><strong>To solve this, you need to add more (or bigger) nodes.</strong></p>
<p>You can also investigate your nodes, e.g. list your nodes with:</p>
<pre><code>kubectl get nodes
</code></pre>
<p>and investigate a specific node (check how many pods it has <em>capacity</em> for - and how many pods that runs on the node) with:</p>
<pre><code>kubectl describe node &lt;node-name&gt;
</code></pre>
