From 5dfbd29a8c6337ffb2ab73e97f5ecd6731f0f01f Mon Sep 17 00:00:00 2001 From: Carson A Date: Wed, 20 Apr 2016 14:36:02 -0600 Subject: [PATCH] Update description to match yaml The tag matching description didn't match the example yaml. --- docs/user-guide/node-selection/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/user-guide/node-selection/index.md b/docs/user-guide/node-selection/index.md index c109f2046c..e4f707dbac 100644 --- a/docs/user-guide/node-selection/index.md +++ b/docs/user-guide/node-selection/index.md @@ -73,8 +73,8 @@ Here's an example of a pod that uses node affinity: This node affinity rule says the pod can only be placed on a node with a label whose key is `kubernetes.io/e2e-az-name` and whose value is either `e2e-az1` or `e2e-az2`. In addition, -among nodes that meet that criteria, nodes with a label whose key is `foo` and whose -value is `bar` should be preferred. +among nodes that meet that criteria, nodes with a label whose key is `another-annotation-key` and whose +value is `another-annotation-value` should be preferred. You can see the operator `In` being used in the example. The new node affinity syntax supports the following operators: `In`, `NotIn`, `Exists`, `DoesNotExist`, `Gt`, `Lt`.