From fc202da36be4d1de52b1ed7408ebe58dca30f249 Mon Sep 17 00:00:00 2001 From: Pierre Laporte Date: Mon, 14 Dec 2020 11:41:52 +0100 Subject: [PATCH] Clarify pod anti-affinity description The code example uses `preferredDuringScheduling...`, as opposed to `requiredDuringScheduling...`. So the anti-affinity rule is a soft one. It says that the pod _should_ not be scheduled on [...] rather than that the pod _cannot_ be scheduled on [...]. --- content/en/docs/concepts/scheduling-eviction/assign-pod-node.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/scheduling-eviction/assign-pod-node.md b/content/en/docs/concepts/scheduling-eviction/assign-pod-node.md index e684b6ea60..abe4f4b9eb 100644 --- a/content/en/docs/concepts/scheduling-eviction/assign-pod-node.md +++ b/content/en/docs/concepts/scheduling-eviction/assign-pod-node.md @@ -246,7 +246,7 @@ as at least one already-running pod that has a label with key "security" and val on node N if node N has a label with key `topology.kubernetes.io/zone` and some value V such that there is at least one node in the cluster with key `topology.kubernetes.io/zone` and value V that is running a pod that has a label with key "security" and value "S1".) The pod anti-affinity -rule says that the pod cannot be scheduled onto a node if that node is in the same zone as a pod with +rule says that the pod should not be scheduled onto a node if that node is in the same zone as a pod with label having key "security" and value "S2". See the [design doc](https://git.k8s.io/community/contributors/design-proposals/scheduling/podaffinity.md) for many more examples of pod affinity and anti-affinity, both the `requiredDuringSchedulingIgnoredDuringExecution`