From cf0eb260cac1664c5f78451d43dbe6b133478611 Mon Sep 17 00:00:00 2001 From: Ti Chi Robot Date: Mon, 11 Sep 2023 17:06:14 +0800 Subject: [PATCH] Clarify use of topologySpreadConstraints (#2448) (#2449) --- en/configure-a-tidb-cluster.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/en/configure-a-tidb-cluster.md b/en/configure-a-tidb-cluster.md index ab3db5cc2..67f773bee 100644 --- a/en/configure-a-tidb-cluster.md +++ b/en/configure-a-tidb-cluster.md @@ -782,7 +782,7 @@ By configuring `topologySpreadConstraints`, you can make pods evenly spread in d To use `topologySpreadConstraints`, you must meet the following conditions: - Your Kubernetes cluster uses `default-scheduler` instead of `tidb-scheduler`. For details, refer to [tidb-scheduler and default-scheduler](tidb-scheduler.md#tidb-scheduler-and-default-scheduler). -- Your Kubernetes cluster enables the `EvenPodsSpread` feature gate. If the Kubernetes version in use is earlier than v1.16 or if the `EvenPodsSpread` feature gate is disabled, the configuration of `topologySpreadConstraints` does not take effect. +- Your Kubernetes cluster enables the `EvenPodsSpread` feature gate if your Kubernetes version is between v1.16 and v1.21. If the Kubernetes version is earlier than v1.16 or if the `EvenPodsSpread` feature gate is disabled, the configuration of `topologySpreadConstraints` does not take effect. If the Kubernetes version is v1.22 and above, you can ignore this condition. You can either configure `topologySpreadConstraints` at a cluster level (`spec.topologySpreadConstraints`) for all components or at a component level (such as `spec.tidb.topologySpreadConstraints`) for specific components.