Merge pull request #41604 from shyamjvs/kubemark-num-nodes

Automatic merge from submit-queue

Reduce default value of kubemark's NUM_NODES to 10

Changing the default value of kubemark's NUM_NODES from 100 to 10, as it would then be possible to start kubemark on gce clusters that have been started using kube-up that uses the default config of three n1-standard-2 nodes. I've already been asked by a couple of people about why kubemark is not starting on their cluster because of this. More people shouldn't be facing this issue in future.

cc @kubernetes/sig-scalability-misc @wojtek-t @gmarek
This commit is contained in:
Kubernetes Submit Queue 2017-02-17 06:49:21 -08:00 committed by GitHub
commit 3b14667afe

View File

@ -25,7 +25,7 @@ GCLOUD=gcloud
ZONE=${KUBE_GCE_ZONE:-us-central1-b}
REGION=${ZONE%-*}
# KUBEMARK_NUM_NODES overrides NUM_NODES if set
NUM_NODES=${KUBEMARK_NUM_NODES:-${NUM_NODES:-100}}
NUM_NODES=${KUBEMARK_NUM_NODES:-${NUM_NODES:-10}}
# KUBEMARK_MASTER_SIZE overrides MASTER_SIZE if set
MASTER_SIZE=${KUBEMARK_MASTER_SIZE:-${MASTER_SIZE:-n1-standard-$(get-master-size)}}
MASTER_DISK_TYPE=pd-ssd