From 74d5af68aea3c82bfbc15d982ba6a331a7eb900d Mon Sep 17 00:00:00 2001 From: Guangya Liu Date: Sat, 8 Apr 2017 18:46:00 +0800 Subject: [PATCH] Added hyperlink for [Interlude: built-in node labels]. --- docs/concepts/configuration/assign-pod-node.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/concepts/configuration/assign-pod-node.md b/docs/concepts/configuration/assign-pod-node.md index 2da39b4b9b..19d4a3a0c7 100644 --- a/docs/concepts/configuration/assign-pod-node.md +++ b/docs/concepts/configuration/assign-pod-node.md @@ -149,7 +149,7 @@ as a LabelSelector with an associated list of namespaces (or "all" namespaces); a label selector over pod labels must specify which namespaces the selector should apply to. Conceptually X is a topology domain like node, rack, cloud provider zone, cloud provider region, etc. You express it using a `topologyKey` which is the key for the node label that the system uses to denote such a topology domain, e.g. see the label keys listed above -in the section "Interlude: built-in node labels." +in the section [Interlude: built-in node labels](#interlude-built-in-node-labels). As with node affinity, there are currently two types of pod affinity and anti-affinity, called `requiredDuringSchedulingIgnoredDuringExecution` and `preferredDuringSchedulingIgnoredDuringExecution` which denote "hard" vs. "soft" requirements.