<p dir="auto"><strong>Is this a request for help?</strong> (If yes, you should use our troubleshooting guide and community support channels, see <a href="http://kubernetes.io/docs/troubleshooting/" rel="nofollow">http://kubernetes.io/docs/troubleshooting/</a>.): yes</p>
<p dir="auto"><strong>What keywords did you search in Kubernetes issues before filing this one?</strong> (If you have found any duplicates, you should instead reply there.): Kubernetes deployed nodes limitation.</p>
<hr>
<p dir="auto"><strong>Is this a BUG REPORT or FEATURE REQUEST?</strong> (choose one): Bug report</p>

<p dir="auto"><strong>Kubernetes version</strong> (use <code class="notranslate">kubectl version</code>): v1.4.3 Server and v1.5.0-alpha Client.</p>
<p dir="auto"><strong>Environment</strong>:</p>
<ul dir="auto">
<li><strong>Cloud provider or hardware configuration</strong>: Huawei Bare metal Server</li>
<li><strong>OS</strong> (e.g. from /etc/os-release): Ubuntu 14.04</li>
<li><strong>Kernel</strong> (e.g. <code class="notranslate">uname -a</code>): 3.16</li>
<li><strong>Install tools</strong>: python, htop, etcd 2.1</li>
<li><strong>Others</strong>: none</li>
</ul>
<p dir="auto"><strong>What happened</strong>: Master node deployed Worker/Node reach 135 Nodes. Now you can't access to master node anymore e.g. $kubectl get node<br>
errors message: Unable to connect to Server: dial tcp [::1]:8080: i/o timeout.</p>
<p dir="auto"><strong>What you expected to happen</strong>: Should be able to execute $kubectl get node with no issue.</p>
<p dir="auto">Unable to connect to Server: dial tcp [::1]:8080: i/o timeout.<br>
<strong>How to reproduce it</strong> (as minimally and precisely as possible):Assume that  your config-default.sh with more than 150 nodes. then execute $KUBERNETES_PROVIDER=ubuntu ./kube-up.sh</p>
<p dir="auto"><strong>Anything else do we need to know</strong>: None</p>
<p dir="auto"><strong>Is this a request for help?</strong> (If yes, you should use our troubleshooting guide and community support channels, see <a href="http://kubernetes.io/docs/troubleshooting/" rel="nofollow">http://kubernetes.io/docs/troubleshooting/</a>.):</p>
<p dir="auto">No</p>
<p dir="auto"><strong>What keywords did you search in Kubernetes issues before filing this one?</strong> (If you have found any duplicates, you should instead reply there.):</p>
<p dir="auto">fit failure on node nodeSelector</p>
<hr>
<p dir="auto"><strong>Is this a BUG REPORT or FEATURE REQUEST?</strong> (choose one):</p>
<p dir="auto">BUG REPORT</p>

<p dir="auto"><strong>Kubernetes version</strong> (use <code class="notranslate">kubectl version</code>):</p>
<p dir="auto"><code class="notranslate">root@melbourne:~/obm-hl-sl/vp0# kubectl version Client Version: version.Info{Major:"1", Minor:"4", GitVersion:"v1.4.0", GitCommit:"a16c0a7f71a6f93c7e0f222d961f4675cd97a46b", GitTreeState:"clean", BuildDate:"2016-09-26T18:16:57Z", GoVersion:"go1.6.3", Compiler:"gc", Platform:"linux/amd64"} Server Version: version.Info{Major:"1", Minor:"4", GitVersion:"v1.4.0", GitCommit:"a16c0a7f71a6f93c7e0f222d961f4675cd97a46b", GitTreeState:"clean", BuildDate:"2016-09-26T18:10:32Z", GoVersion:"go1.6.3", Compiler:"gc", Platform:"linux/amd64"} </code></p>
<p dir="auto"><strong>Environment</strong>:</p>
<ul dir="auto">
<li><strong>Cloud provider or hardware configuration</strong>: Softlayer</li>
<li><strong>OS</strong> (e.g. from /etc/os-release):<br>
<code class="notranslate">root@melbourne:~/obm-hl-sl/vp0# cat /etc/os-release NAME="Ubuntu" VERSION="16.04.1 LTS (Xenial Xerus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04.1 LTS" VERSION_ID="16.04" HOME_URL="http://www.ubuntu.com/" SUPPORT_URL="http://help.ubuntu.com/" BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/" UBUNTU_CODENAME=xenial </code></li>
<li><strong>Kernel</strong> (e.g. <code class="notranslate">uname -a</code>): 'Linux melbourne.artlab.anz.com 4.4.0-38-generic <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="35453339" data-permission-text="Title is private" data-url="https://github.com/kubernetes/kubernetes/issues/57" data-hovercard-type="pull_request" data-hovercard-url="/kubernetes/kubernetes/pull/57/hovercard" href="https://github.com/kubernetes/kubernetes/pull/57">#57</a>-Ubuntu SMP Tue Sep 6 15:42:33 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux'</li>
<li><strong>Install tools</strong>: 'kubeadm'</li>
<li><strong>Others</strong>:</li>
</ul>
<p dir="auto"><strong>What happened</strong>:</p>
<ol dir="auto">
<li>Label a node with 'kubectl label nodes melbourne.artlab.anz.com node=node-vp0'</li>
<li>Use the attached files to create a Deployment.</li>
<li>The Deployment used 'nodeSelector:' with 'node: node-vp' to select which node to run the pod on.</li>
<li>Error occurs when 'kubectl create -f dep-hl-vp0.yml -n hyperledger'</li>
<li>Error is <code class="notranslate">pod (dep-pod-hl-vp0-1977689428-9veze) failed to fit in any node fit failure on node (hongkong.artlab.anz.com): MatchNodeSelector fit failure on node (melbourne.artlab.anz.com): PodToleratesNodeTaints fit failure on node (singapore.artlab.anz.com): MatchNodeSelector fit failure on node (sydney.artlab.anz.com): MatchNodeSelector</code></li>
</ol>
<p dir="auto"><strong>What you expected to happen</strong>:</p>
<p dir="auto">I expected the pod to be created on the node with the label 'node: node-vp'</p>
<p dir="auto"><strong>How to reproduce it</strong> (as minimally and precisely as possible):</p>
<ol dir="auto">
<li>Install Kubernetes v.1.4</li>
<li>Label a node with 'kubectl label nodes  node=node-vp0'</li>
<li>Run 'kubectl create -f ns-hl.yml'</li>
<li>Run 'kubectl create -f svc-hl-vp0.yml  -n hyperledger'</li>
<li>Run 'kubectl create -f dep-hl-vp0.yml -n hyperledger'</li>
</ol>
<p dir="auto"><strong>Anything else do we need to know</strong>:</p>
<p dir="auto">These manifest files work on GKE.</p>