title: Pod limit on Node - AWS EKS
body: <p>On AWS EKS
  I'm adding deployment with 17 replicas (requesting and limiting 64Mi memory) to a small cluster with 2 nodes type t3.small.</p>
  
  <p>Counting with kube-system pods, total running pods per node is 11 and 1 is left pending, i.e.:</p>
  
  <p>Node #1: <br>
  aws-node-1<br>
  coredns-5-1as3<br>
  coredns-5-2das<br>
  kube-proxy-1<br>
  +7 app pod replicas       <br>
  <br>
  Node #2:<br>
  aws-node-1<br>
  kube-proxy-1<br>
  +9 app pod replicas<br>
  <br>
  I understand that t3.small is a very small instance. I'm only trying to understand what is limiting me here. Memory request is not it, I'm way below the available resources.</p>
  
  <p>I found that there is IP addresses limit per node depending on instance type.
  <a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-eni.html?shortFooter=true#AvailableIpPerENI" rel="noreferrer">https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-eni.html?shortFooter=true#AvailableIpPerENI</a> .<br>
  I didn't find any other documentation saying explicitly that this is limiting pod creation, but I'm assuming it does.
  Based on the table, t3.small can have 12 IPv4 addresses. If this is the case and this is limiting factor, since I have 11 pods, where did 1 missing IPv4 address go?</p>