Skip to content

Commit 648e1e4

Browse files
committed
Replaced pod anti-affinity with pod topology spread constraints
1 parent bada247 commit 648e1e4

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/aks/best-practices-app-cluster-reliability.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -181,9 +181,9 @@ For more information, see [Max Unavailable](https://kubernetes.io/docs/concepts/
181181

182182
> **Best practice guidance**
183183
>
184-
> Use pod topology spread constraints to ensure that pods are spread across different nodes, zones, or regions to improve availability and reliability.
184+
> Use pod topology spread constraints to ensure that pods are spread across different nodes or zones to improve availability and reliability.
185185

186-
You can use pod topology spread constraints to control how pods are spread across your cluster based on the topology of the nodes. You can use topology spread constraints to spread pods across different nodes, zones, or regions to improve availability and reliability.
186+
You can use pod topology spread constraints to control how pods are spread across your cluster based on the topology of the nodes and spread pods across different nodes or zones to improve availability and reliability.
187187

188188
The following example pod definition file shows how to use the `topologySpreadConstraints` field to spread pods across different nodes:
189189

0 commit comments

Comments
 (0)