From 80634870918718eeaef5ca5adde145777b853105 Mon Sep 17 00:00:00 2001 From: Nitish Kumar <86051118+NitishKumar06@users.noreply.github.com> Date: Sun, 29 May 2022 11:27:21 +0530 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Qiming Teng --- .../en/docs/concepts/scheduling-eviction/assign-pod-node.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) 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 473d158e43..b5a786620b 100644 --- a/content/en/docs/concepts/scheduling-eviction/assign-pod-node.md +++ b/content/en/docs/concepts/scheduling-eviction/assign-pod-node.md @@ -302,8 +302,8 @@ the Pod onto a node that is in the same zone as one or more Pods with the label `topology.kubernetes.io/zone=R` label if there are other nodes in the same zone currently running Pods with the `Security=S2` Pod label. -To get yourself more familiar with the examples of Pod affinity and anti-affinity -Refer to this [link](https://github.com/kubernetes/design-proposals-archive/blob/main/scheduling/podaffinity.md) +To get yourself more familiar with the examples of Pod affinity and anti-affinity, +refer to the [design proposal](https://github.com/kubernetes/design-proposals-archive/blob/main/scheduling/podaffinity.md). You can use the `In`, `NotIn`, `Exists` and `DoesNotExist` values in the `operator` field for Pod affinity and anti-affinity.