docs(concepts): Clarify podAffinity/podAntiAffinity note (#948)

* docs(concepts): Clarify podAffinity/podAntiAffinity note * Change KEP section * Update website/content/en/docs/concepts/_index.md Co-authored-by: Maxime Brunet <[email protected]> Co-authored-by: Ellis Tarn <[email protected]>
aws · Dec 8, 2021 · 0e6633f · 0e6633f
1 parent 7f2fcda
commit 0e6633f
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/website/content/en/docs/concepts/_index.md b/website/content/en/docs/concepts/_index.md
@@ -157,7 +157,7 @@ Those that are implemented in Karpenter include:
 
 {{% alert title="Note" color="primary" %}}
 Don't use `podAffinity` and `podAntiAffinity` to schedule pods on the same or different nodes as other pods.
-Kubernetes SIG scalability recommends against these features and Karpenter doesn't support them.
+Kubernetes SIG scalability recommends against these features due to their negative performance impact on the Kubernetes Scheduler (see [KEP 895](https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/895-pod-topology-spread#impact-to-other-features)) and Karpenter doesn't support them for the moment (you can follow their consideration by subscribing to the [issue](https://github.com/aws/karpenter/issues/942)).".
 Instead, the Karpenter project recommends `topologySpreadConstraints` to reduce blast radius and `nodeSelectors` and `taints` to implement colocation.
 {{% /alert %}}