Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • NUM_NODES=5, suggested_master_size=2
  • NUM_NODES=10, suggested_master_size=4
  • NUM_NODES=100, suggested_master_size=8
  • NUM_NODES=250, suggested_master_size=16
  • NUM_NODES=500, suggested_master_size=32

This is actually the node size. There's no indication that either GCE and AWS use multiple masters, just bigger masters – even with hundred-node setups.

config-default.sh

  • NODE_SIZE=n1-standard-2
  • NUM_NODES=3
  • MASTER_DISK_SIZE=20GB
  • NODE_DISK_SIZE=100GB

The GCE setup in kubernetes seems to Kubernetes does not indicate separate servers for etcd for events, but etcd on master?they do mention using a separate etcd for events.

See also

Heapster scalability testing

 

GET operations do not always work on 500 node GCE cluster

API status for pods is flaky