http://kubernetes.io/docs/admin/cluster-large/
Minimum cluster size
David has suggested the following minimum cluster size:
- 3 etcd (m1.small)
- 1 master (m1.medium)
- 3-4 compute
- 4 gfs (m1.medium)
GCE sizing
The file kubernetes/cluster/gce/config-common.sh contains the following:
- 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 does not indicate separate servers for etcd, but they do mention using a separate etcd for events.
See also
GET operations do not always work on 500 node GCE cluster
http://kubernetes.io/docs/admin/high-availability/#master-elected-components
https://github.com/kubernetes/kubernetes/blob/release-1.2/docs/proposals/scalability-testing.md
http://blog.kubernetes.io/2015/09/kubernetes-performance-measurements-and.html
https://github.com/kubernetes/kubernetes/blob/release-1.2/docs/devel/node-performance-testing.md
https://github.com/kubernetes/kubernetes/blob/release-1.2/test/e2e/kubelet_perf.go
http://kubernetes.io/docs/admin/high-availability/
Gluster
http://www.gluster.org/community/documentation/index.php/QuickStart
"Have at least two nodes"
Performance monitoring