From ede08e612bf465f4d47179ed42a646acad4325f3 Mon Sep 17 00:00:00 2001 From: Adhityaa Chandrasekar Date: Wed, 28 Oct 2020 11:02:04 +0000 Subject: [PATCH] pod topology spread: add note about GA and feature gates Signed-off-by: Adhityaa Chandrasekar --- .../pods/pod-topology-spread-constraints.md | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) 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 5cc52cdbe6..1dd791d377 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 @@ -4,11 +4,21 @@ content_type: concept weight: 40 --- +{{< feature-state for_k8s_version="v1.19" state="stable" >}} + + 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.19, 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/generated/kube-scheduler/) in order to use Pod +topology spread constraints. +{{< /note >}}