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

Fix the typo (#18732)

Browse Source 
"AND of exact match" in the "Affinity and anti-affinity" section should be "AND or exact match"
This commit is contained in:
Alexander Zhukov
2020-01-17 01:32:43 +02:00
committed by Kubernetes Prow Robot
parent 8aba9c656b
commit f5bfa04aa4
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
@@ -111,7 +111,7 @@ For example, `example.com.node-restriction.kubernetes.io/fips=true` or `example.
`nodeSelector` provides a very simple way to constrain pods to nodes with particular labels. The affinity/anti-affinity `nodeSelector` provides a very simple way to constrain pods to nodes with particular labels. The affinity/anti-affinity
feature, greatly expands the types of constraints you can express. The key enhancements are feature, greatly expands the types of constraints you can express. The key enhancements are
1. the language is more expressive (not just "AND of exact match") 1. the language is more expressive (not just "AND or exact match")
2. you can indicate that the rule is "soft"/"preference" rather than a hard requirement, so if the scheduler 2. you can indicate that the rule is "soft"/"preference" rather than a hard requirement, so if the scheduler
can't satisfy it, the pod will still be scheduled can't satisfy it, the pod will still be scheduled
3. you can constrain against labels on other pods running on the node (or other topological domain), 3. you can constrain against labels on other pods running on the node (or other topological domain),