As posted in the comments:

Please add to the question the steps that you followed (editing any values in the Helm chart etc). Also please check if the nodes are not over the limit of pods that can be scheduled on it. Here you can find the link for more reference: LINK.

no processes occupying 9100 on the given node. @DawidKruk The POD limit was reached. Thanks! I expected them to give me some error regarding that rather than vague node selector property not matching


Not really sure why the following messages were displayed:

  • node(s) didn’t have free ports for the requested pod ports
  • node(s) didn’t match node selector

The issue that Pods couldn’t be scheduled on the nodes (Pending state) was connected with the Insufficient pods message in the $ kubectl get events command.

Above message is displayed when the nodes reached their maximum capacity of pods (example: node1 can schedule maximum of 30 pods).


More on the Insufficient Pods can be found in this github issue comment:

That’s true. That’s because the CNI implementation on EKS. Max pods number is limited by the network interfaces attached to instance multiplied by the number of ips per ENI – which varies depending on the size of instance. It’s apparent for small instances, this number can be quite a low number.

Docs.aws.amazon.com: AWSEC2: User Guide: Using ENI: Available IP per ENI

Github.com: Kubernetes: Autoscaler: Issue 1576: Comment 454100551


Additional resources:

CLICK HERE to find out more related problems solutions.

Leave a Comment

Your email address will not be published.

Scroll to Top