Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GKE master size is not usually fix, this documentation assumes it is #9276

Closed
wants to merge 2 commits into from
Closed

GKE master size is not usually fix, this documentation assumes it is #9276

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3c5b0e8
GKE master size is not usually fix, this documentation assumes it is
kmassada Jun 27, 2018
95a1c58
GKE master size is not usually fix, this documentation assumes it is
kmassada Jun 27, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion content/en/docs/setup/cluster-large.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -74,7 +74,7 @@ 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 that these master node sizes are currently only set at cluster startup time, and may be adjusted if you later scale your cluster up or down (e.g. manually removing or adding nodes, or using a cluster autoscaler), depending on GCE/Google Kubernetes Engine, and AWS implementation.

### Addon Resources

Expand Down