diff options
| author | Crazykev <crazykev@zju.edu.cn> | 2016-08-10 15:43:27 +0800 |
|---|---|---|
| committer | Crazykev <crazykev@zju.edu.cn> | 2016-08-10 15:43:27 +0800 |
| commit | de3f3fa1e46e54ab1640721035ec8609cd210bea (patch) | |
| tree | 8e5a7119986446291a6a974dc286e7bae91cd938 | |
| parent | 13213ad729334c7d77c4039b822c342fe0bf5cd5 (diff) | |
fix a typo in nodeaffinity
Signed-off-by: Crazykev <crazykev@zju.edu.cn>
| -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 |