From f160db17d605385cc5654929b45af10193fdf8a9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bj=C3=B6rn=20Svensson?= Date: Wed, 15 Sep 2021 12:38:40 +0200 Subject: [PATCH] PodTopology: add notes of possible changed default behavior MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Björn Svensson --- .../workloads/pods/pod-topology-spread-constraints.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/content/en/docs/concepts/workloads/pods/pod-topology-spread-constraints.md b/content/en/docs/concepts/workloads/pods/pod-topology-spread-constraints.md index 4e69837503..47176e885b 100644 --- a/content/en/docs/concepts/workloads/pods/pod-topology-spread-constraints.md +++ b/content/en/docs/concepts/workloads/pods/pod-topology-spread-constraints.md @@ -349,12 +349,14 @@ Also, the legacy `SelectorSpread` plugin, which provides an equivalent behavior, is disabled. {{< note >}} +The `PodTopologySpread` plugin does not score the nodes that don't have +the topology keys specified in the spreading constraints. This might result +in a different default behavior compared to the legacy `SelectorSpread` plugin when +using the default topology constraints. + If your nodes are not expected to have **both** `kubernetes.io/hostname` and `topology.kubernetes.io/zone` labels set, define your own constraints instead of using the Kubernetes defaults. - -The `PodTopologySpread` plugin does not score the nodes that don't have -the topology keys specified in the spreading constraints. {{< /note >}} If you don't want to use the default Pod spreading constraints for your cluster,