From b8f1eb223f2cc47c966a5d34fb3f93330c0c0323 Mon Sep 17 00:00:00 2001 From: Crazykev Date: Wed, 10 Aug 2016 15:43:27 +0800 Subject: [PATCH] fix a typo in nodeaffinity Signed-off-by: Crazykev --- docs/design/nodeaffinity.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/design/nodeaffinity.md b/docs/design/nodeaffinity.md index f1bfec6f0b5..1459a321dfa 100644 --- a/docs/design/nodeaffinity.md +++ b/docs/design/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