From f0e4a10636176626141f2011a209893d47032b00 Mon Sep 17 00:00:00 2001 From: Mitesh Jain <47820816+miteshskj@users.noreply.github.com> Date: Wed, 30 Mar 2022 21:24:51 +0530 Subject: [PATCH] Remove note for unsupported version. --- .../workloads/pods/pod-topology-spread-constraints.md | 8 -------- 1 file changed, 8 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 4823cd26f5..369c81eb8d 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 @@ -12,14 +12,6 @@ obsolete --> You can use _topology spread constraints_ to control how {{< glossary_tooltip text="Pods" term_id="Pod" >}} are spread across your cluster among failure-domains such as regions, zones, nodes, and other user-defined topology domains. This can help to achieve high availability as well as efficient resource utilization. -{{< note >}} -In versions of Kubernetes before v1.18, you must enable the `EvenPodsSpread` -[feature gate](/docs/reference/command-line-tools-reference/feature-gates/) on -the [API server](/docs/concepts/overview/components/#kube-apiserver) and the -[scheduler](/docs/reference/command-line-tools-reference/kube-scheduler/) in order to use Pod -topology spread constraints. -{{< /note >}} - ## Prerequisites