You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You could try to calculate it, and the formula would be Max IPs - Max ENIs + 2
(You could also do Max ENIs * (IPs per ENI - 1) + 2, it equates to the same.
See https://stackoverflow.com/questions/57970896/pod-limit-on-node-aws-eks)
And that works for 99% of the Instances Types, but for some exotic Instance Types that does not work, eg:
This would be of great help, as right I can find the ideal Instance Types for my k8s, and when I want to use them, I get errors because I can't place all my pods on them. (we have many pods that require little CPU and RAM, and for a Dev Cluster we only need 3 Nodes..)
There is also this script which is present on all managed nodes:
/etc/eks/max-pods-calculator.sh --help
usage: /etc/eks/max-pods-calculator.sh <instance(s)> [options]
Calculates maxPods value to be used when starting up the kubelet.
-h,--help print this help.
--instance-type Specify the instance type to calculate max pods value.
--instance-type-from-imds Use this flag if the instance type should be fetched from IMDS.
--cni-version Specify the version of the CNI (example - 1.7.5).
--cni-custom-networking-enabled Use this flag to indicate if CNI custom networking mode has been enabled.
--cni-prefix-delegation-enabled Use this flag to indicate if CNI prefix delegation has been enabled.
--cni-max-eni specify how many ENIs should be used for prefix delegation. Defaults to using all ENIs per instance.
--show-max-allowed Use this flag to show max number of Pods allowed to run in Worker Node. Otherwise the script will show the recommended value
Although it's a number that can be calculated from existing data, would it be possible to add the information from this document: https://github.com/awslabs/amazon-eks-ami/blob/master/files/eni-max-pods.txt ?
Thanks!
The text was updated successfully, but these errors were encountered: