Skip to content

Commit

Permalink
Update multiple-zones.md
Browse files Browse the repository at this point in the history
  • Loading branch information
yanrongshi committed Jul 25, 2022
1 parent 9f1bf2c commit 8db75a7
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions content/zh-cn/docs/setup/best-practices/multiple-zones.md
Original file line number Diff line number Diff line change
Expand Up @@ -113,7 +113,7 @@ These labels can include
<!--
If your cluster spans multiple zones or regions, you can use node labels
in conjunction with
[Pod topology spread constraints](/docs/concepts/workloads/pods/pod-topology-spread-constraints/)
[Pod topology spread constraints](/docs/concepts/scheduling-eviction/topology-spread-constraints/)
to control how Pods are spread across your cluster among fault domains:
regions, zones, and even specific nodes.
These hints enable the
Expand All @@ -122,7 +122,7 @@ Pods for better expected availability, reducing the risk that a correlated
failure affects your whole workload.
-->
如果你的集群跨了多个可用区或者地理区域,你可以使用节点标签,结合
[Pod 拓扑分布约束](/zh-cn/docs/concepts/workloads/pods/pod-topology-spread-constraints/)
[Pod 拓扑分布约束](/zh-cn/docs/concepts/scheduling-eviction/topology-spread-constraints/)
来控制如何在你的集群中多个失效域之间分布 Pods。这里的失效域可以是
地理区域、可用区甚至是特定节点。
这些提示信息使得{{< glossary_tooltip text="调度器" term_id="kube-scheduler" >}}
Expand Down

0 comments on commit 8db75a7

Please sign in to comment.