Skip to content

Commit

Permalink
Fix typo: speficied -> specified (#10395)
Browse files Browse the repository at this point in the history
Signed-off-by: Rui Cao <ruicao@alauda.io>
  • Loading branch information
mirake authored and k8s-ci-robot committed Sep 27, 2018
1 parent 5752bac commit de82a88
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion content/en/docs/concepts/configuration/assign-pod-node.md
Expand Up @@ -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.
Expand Down

0 comments on commit de82a88

Please sign in to comment.