Skip to content

Commit

Permalink
Update information on master node size on GKE/AWS (#9226)
Browse files Browse the repository at this point in the history
* Update information on master node size on GKE/AWS

* clean up passive language
  • Loading branch information
lucperkins authored and k8s-ci-robot committed Jul 25, 2018
1 parent 395aa19 commit 8600631
Showing 1 changed file with 5 additions and 1 deletion.
6 changes: 5 additions & 1 deletion content/en/docs/setup/cluster-large.md
Original file line number Diff line number Diff line change
Expand Up @@ -74,7 +74,11 @@ And the sizes we use on AWS are
* 251-500 nodes: c4.4xlarge
* more than 500 nodes: c4.8xlarge

Note that these master node sizes are currently only set at cluster startup time, and are not adjusted if you later scale your cluster up or down (e.g. manually removing or adding nodes, or using a cluster autoscaler).
{{< note >}}
On Google Kubernetes Engine, the size of the master node adjusts automatically based on the size of your cluster. For more information, see [this blog post](https://cloudplatform.googleblog.com/2017/11/Cutting-Cluster-Management-Fees-on-Google-Kubernetes-Engine.html).

On AWS, master node sizes are currently set at cluster startup time and do not change, even if you later scale your cluster up or down by manually removing or adding nodes or using a cluster autoscaler.
{{< /note >}}

### Addon Resources

Expand Down

0 comments on commit 8600631

Please sign in to comment.