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

Fix typo: speficied -> specified (#10395)

Browse Source 
Signed-off-by: Rui Cao <ruicao@alauda.io>
This commit is contained in:
Rui Cao
2018-09-27 22:08:57 +08:00
committed by k8s-ci-robot
parent 5752bacbfa
commit de82a8820e
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/configuration/assign-pod-node.md
+1 -1
View File
@@ -178,7 +178,7 @@ in the section [Interlude: built-in node labels](#interlude-built-in-node-labels
processing which can slow down scheduling in large clusters significantly. We do processing which can slow down scheduling in large clusters significantly. We do
not recommend using them in clusters larger than several hundred nodes. not recommend using them in clusters larger than several hundred nodes.
**Note:** Pod anti-affinity requires nodes to be consistently labelled, i.e. every node in the cluster must have an appropriate label matching `topologyKey`. If some or all nodes are missing the speficied `topologyKey` label, it can lead to unintended behavior. **Note:** Pod anti-affinity requires nodes to be consistently labelled, i.e. every node in the cluster must have an appropriate label matching `topologyKey`. If some or all nodes are missing the specified `topologyKey` label, it can lead to unintended behavior.
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.