Issue 1:
Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see http://kubernetes.io/docs/troubleshooting/.): yes

What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.): Kubernetes deployed nodes limitation.

Is this a BUG REPORT or FEATURE REQUEST? (choose one): Bug report

Kubernetes version (use kubectl version): v1.4.3 Server and v1.5.0-alpha Client.

Environment:

Cloud provider or hardware configuration: Huawei Bare metal Server

OS (e.g. from /etc/os-release): Ubuntu 14.04

Kernel (e.g. uname -a): 3.16

Install tools: python, htop, etcd 2.1

Others: none

What happened: Master node deployed Worker/Node reach 135 Nodes. Now you can't access to master node anymore e.g. $kubectl get node

errors message: Unable to connect to Server: dial tcp [::1]:8080: i/o timeout.

What you expected to happen: Should be able to execute $kubectl get node with no issue.

Unable to connect to Server: dial tcp [::1]:8080: i/o timeout.

How to reproduce it (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

Anything else do we need to know: None

Issue 2:
Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see http://kubernetes.io/docs/troubleshooting/.):

No

What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.):

fit failure on node nodeSelector

Is this a BUG REPORT or FEATURE REQUEST? (choose one):

BUG REPORT

Kubernetes version (use kubectl version):

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"}

Environment:

Cloud provider or hardware configuration: Softlayer

OS (e.g. from /etc/os-release):

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

Kernel (e.g. uname -a): 'Linux melbourne.artlab.anz.com 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:42:33 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux'

Install tools: 'kubeadm'

Others:

What happened:

Label a node with 'kubectl label nodes melbourne.artlab.anz.com node=node-vp0'

Use the attached files to create a Deployment.

The Deployment used 'nodeSelector:' with 'node: node-vp' to select which node to run the pod on.

Error occurs when 'kubectl create -f dep-hl-vp0.yml -n hyperledger'

Error is 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

What you expected to happen:

I expected the pod to be created on the node with the label 'node: node-vp'

How to reproduce it (as minimally and precisely as possible):

Install Kubernetes v.1.4

Label a node with 'kubectl label nodes node=node-vp0'

Run 'kubectl create -f ns-hl.yml'

Run 'kubectl create -f svc-hl-vp0.yml -n hyperledger'

Run 'kubectl create -f dep-hl-vp0.yml -n hyperledger'

Anything else do we need to know:

These manifest files work on GKE.