Skip to content

Commit 9a31e7a

Browse files
authored
Merge pull request #36400 from cenkalti/patch-1
Fix scaling terminology
2 parents 484f146 + bf99802 commit 9a31e7a

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -314,11 +314,11 @@ ETCDCTL_API=3 etcdctl --endpoints=https://127.0.0.1:2379 \
314314
```
315315
where `trusted-ca-file`, `cert-file` and `key-file` can be obtained from the description of the etcd Pod.
316316

317-
## Scaling up etcd clusters
317+
## Scaling out etcd clusters
318318

319-
Scaling up etcd clusters increases availability by trading off performance.
319+
Scaling out etcd clusters increases availability by trading off performance.
320320
Scaling does not increase cluster performance nor capability. A general rule
321-
is not to scale up or down etcd clusters. Do not configure any auto scaling
321+
is not to scale out or in etcd clusters. Do not configure any auto scaling
322322
groups for etcd clusters. It is highly recommended to always run a static
323323
five-member etcd cluster for production Kubernetes clusters at any officially
324324
supported scale.

0 commit comments

Comments
 (0)