<p>After trying with various providers(bare kubernetes, openshift, aws eks) we have found that even if node has enough resources(cpu, ram, hdd) after reaching ~110 pods new pods are hanging in Pending state without any events or errors except the event </p>

<pre><code>"Successfully assigned {namespace}/{pod_name} to {node_name}"
</code></pre>

<p>We have tried to search for any related logs in kubelet, scheduler, etc - but there is nothing except this event mentioned earlier.</p>

<p>Did someone succeed in running more than 110 pods per node? What are we doing wrong?</p>

<p>The only thing worth mentioning additionally is that in our case it is not 110 replicas of same pod but a 110 various pods from various deployments/daemon sets. And of course we have tweaked node pod_limit > 110.</p>

Stanislav Ogarkov
<p>kunernetes supports 110 pods per node. There are requests coming from multiple channels to increase the pods per node.</p>

<p>There is PR raised to support 500 pods per node. it is still open though. you can track the status at the below link</p>

<p><a href="https://github.com/kubernetes/kubernetes/issues/23349" rel="nofollow noreferrer">PR to support 500 pods per node</a></p>
