From 64da6792e9144fb2a25ab1bd0efc65d77a1bd894 Mon Sep 17 00:00:00 2001 From: tidusete Date: Wed, 30 Mar 2022 18:01:59 +0200 Subject: [PATCH] Missunderstood pods/pod-with-node-affinity.yaml Either we correct the code from pods/pod-with-node-affinity.yaml to match the description about the rules that apply or we correct the description in order to match the pods/pod-with-node-affinity.yaml --- .../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 2e38eb6938..44b3c07164 100644 --- a/content/en/docs/concepts/scheduling-eviction/assign-pod-node.md +++ b/content/en/docs/concepts/scheduling-eviction/assign-pod-node.md @@ -124,8 +124,8 @@ For example, consider the following Pod spec: In this example, the following rules apply: - * The node *must* have a label with the key `kubernetes.io/e2e-az-name` and - the value is either `e2e-az1` or `e2e-az2`. + * The node *must* have a label with the key `kubernetes.io/os` and + the value `linux`. * The node *preferably* has a label with the key `another-node-label-key` and the value `another-node-label-value`.