<p>From the <a href="http://blog.kubernetes.io/2015/09/kubernetes-performance-measurements-and.html" rel="nofollow">performance test report</a> we can find that the <code>kubernetes</code> can support 100 nodes.</p>

<p>To do the same test, I have set up a 100 nodes <code>kubernetes</code> cluster, but the <code>kube-apiserver</code> became slow when the cluster is set up. That meant when I typed <code>kubectl get nodes</code>, it suspended and can not get any respond.</p>

<p>To find the reason, I chech the connections of <code>kube-apiserver</code> and found there were about 660+ ESTABLISHED connections on port 8080 (I used the insecure port of apiserver), and when I stop some(about 20) slaves, the <code>apiserver</code> recovered common. So I thought the reason for <code>kube-apiserver</code> becoming slow is the too large concurrency.</p>

<p>So I am wonder how the Google set up a 100 nodes cluster? Is there something wrong in my work?</p>

<p>PS: The <code>--max-requests-inflight</code> of <code>kube-apiserver</code> has been set to 0.</p>

<p>The doc you link to describes the methodology used (specifically the master VM size). The cluster is created in Google Compute Engine using the default cluster/kube-up.sh script from the repository, with all the default settings implied by that.</p>

<p>How large is the master that you're using? If it's really small, it's possible that it could struggle with a lot of nodes and pods.</p>
