Github repo:

But the pods took hours and still in PENDING state, and when I run the command kubectl describe pod <POD_NAME> I get the follwing info

reverseproxy-667b78569b-2c6hv pod: https://pastebin.com/3xF04SEx
udagram-api-feed-856bbc5c45-jcgtk pod: https://pastebin.com/5UqB79tU
udagram-api-users-6fbd5cbf4f-qbmdd pod: https://pastebin.com/Hiqe1LAM

CodePudding user response：

From your kubectl describe pod <podname>

Warning FailedScheduling 2m19s (x136 over 158m) default-scheduler 0/2 nodes are available: 2 Too many pods.

When you see this, it means that your nodes in AWS EKS is full.

To solve this, you need to add more (or bigger) nodes.

You can also investigate your nodes, e.g. list your nodes with:

kubectl get nodes

and investigate a specific node (check how many pods it has capacity for - and how many pods that runs on the node) with:

kubectl describe node <node-name>