diff options
| author | Kubernetes Submit Queue <k8s-merge-robot@users.noreply.github.com> | 2016-08-15 13:10:18 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2016-08-15 13:10:18 -0700 |
| commit | 1420871bd108748c2e3a8ff4af36d077f548dae2 (patch) | |
| tree | 7505983c1ad92abf86f57cad36cc46f07b740d7c /nodeaffinity.md | |
| parent | a200c44d2dbb133c24046558978e4a5ecb815243 (diff) | |
| parent | de3f3fa1e46e54ab1640721035ec8609cd210bea (diff) | |
Merge pull request #30343 from Crazykev/fix-spelling
Automatic merge from submit-queue
fix a typo in nodeaffinity
Diffstat (limited to 'nodeaffinity.md')
| -rw-r--r-- | nodeaffinity.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/nodeaffinity.md b/nodeaffinity.md index f1bfec6f..1459a321 100644 --- a/nodeaffinity.md +++ b/nodeaffinity.md @@ -69,7 +69,7 @@ an Intel CPU" or, in a multi-zone cluster, "run this pod on a node in zone Z." some of the properties that a node might publish as labels, which affinity expressions can match against.) They do *not* allow a pod to request to schedule (or not schedule) on a node based on what other pods are running on the node. -That feature is called "inter-pod topological affinity/anti-afinity" and is +That feature is called "inter-pod topological affinity/anti-affinity" and is described [here](https://github.com/kubernetes/kubernetes/pull/18265). ## API |