From c57ac35209bd03de6b9bdff22149f4f7663a295e Mon Sep 17 00:00:00 2001 From: Stephan van Maris Date: Thu, 21 Dec 2017 16:39:20 +0100 Subject: [PATCH] AnitAffinity -> AntiAffinity --- docs/concepts/configuration/assign-pod-node.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/concepts/configuration/assign-pod-node.md b/docs/concepts/configuration/assign-pod-node.md index c6fc8ebf3a..df6ace536b 100644 --- a/docs/concepts/configuration/assign-pod-node.md +++ b/docs/concepts/configuration/assign-pod-node.md @@ -212,7 +212,7 @@ must be satisfied for the pod to schedule onto a node. #### More Practical Use-cases -Interpod Affinity and AnitAffinity can be even more useful when they are used with higher +Interpod Affinity and AntiAffinity can be even more useful when they are used with higher level collections such as ReplicaSets, Statefulsets, Deployments, etc. One can easily configure that a set of workloads should be co-located in the same defined topology, eg., the same node.