Skip to content

Commit 29801cc

Browse files
authored
Merge pull request #25340 from gavinfish/zone-revise
Revise running in multiple zones
2 parents 1081c4d + a6e8f8b commit 29801cc

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

content/en/docs/setup/best-practices/multiple-zones.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ support running as a pool of interchangable resources, replicated per
3333
component.
3434

3535
When you deploy a cluster control plane, place replicas of
36-
control plane components across multple failure zones. If availability is
36+
control plane components across multiple failure zones. If availability is
3737
an important concern, select at least three failure zones and replicate
3838
each individual control plane component (API server, scheduler, etcd,
3939
cluster controller manager) across at least three failure zones.
@@ -126,7 +126,7 @@ of different failure zones, does vary depending on exactly how your cluster is s
126126
## Fault recovery
127127

128128
When you set up your cluster, you might also need to consider whether and how
129-
your setup can restore service if all of the failure zones in a region go
129+
your setup can restore service if all the failure zones in a region go
130130
off-line at the same time. For example, do you rely on there being at least
131131
one node able to run Pods in a zone?
132132
Make sure that any cluster-critical repair work does not rely

0 commit comments

Comments
 (0)