kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Fix scaling terminology 

Replace scale `up/down` terminology with `out/in` as the point is about adding more nodes to the cluster.

- https://azure.microsoft.com/en-us/solutions/scaling-out-vs-scaling-up/
- https://www.dell.com/en-us/blog/the-difference-between-scale-up-and-scale-out/
pull/36400/head
Cenk Altı 2022-08-29 15:15:53 -04:00 committed by GitHub
parent e46f6685f2
commit bf998026d2
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
content/en/docs/tasks/administer-cluster/configure-upgrade-etcd.md
View File

@ -314,11 +314,11 @@ ETCDCTL_API=3 etcdctl --endpoints=https://127.0.0.1:2379 \
```
where `trusted-ca-file`, `cert-file` and `key-file` can be obtained from the description of the etcd Pod.
## Scaling up etcd clusters
## Scaling out etcd clusters
Scaling up etcd clusters increases availability by trading off performance.
Scaling out etcd clusters increases availability by trading off performance.
Scaling does not increase cluster performance nor capability. A general rule
is not to scale up or down etcd clusters. Do not configure any auto scaling
is not to scale out or in etcd clusters. Do not configure any auto scaling
groups for etcd clusters. It is highly recommended to always run a static
five-member etcd cluster for production Kubernetes clusters at any officially
supported scale.