Pending Pods: Limits in EKS
Updated: Jul 11
It is annoying to finally deploy our application in an EKS cluster to get the eternal “pending” state of our pods.
Several reasons might get a pod in a pending state; most of them are related to computing resource limits, but some others are related to IP address limits in our worker nodes.
However, reaching this kind of limit is an easy problem to solve. You can find the right type of instance for your Kubernetes workloads by checking this handy document provided by AWS. https://github.com/awslabs/amazon-eks-ami/blob/master/files/eni-max-pods.txt to have the maximum number of pods per instance, and best of all, not only a few but all AWS EKS instances available.
So, If you want to avoid some frustrations and headaches, that document will be a good starting point!
Come back later for more Teratips about EKS.
Leandro Mansilla
DevOps Engineer
Teracloud
