whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Added hyperlink for [Interlude: built-in node labels].

Browse Source
This commit is contained in:
Guangya Liu
2017-04-08 18:46:00 +08:00
committed by Andrew Chen
parent 857c321f74
commit 74d5af68ae
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/concepts/configuration/assign-pod-node.md
+1 -1
View File
@@ -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 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 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 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 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. `preferredDuringSchedulingIgnoredDuringExecution` which denote "hard" vs. "soft" requirements.