From 0e6633fe6c815ec218d7e8a79b022a3ea8550302 Mon Sep 17 00:00:00 2001 From: Maxime Brunet Date: Wed, 8 Dec 2021 15:07:18 -0800 Subject: [PATCH] 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 Co-authored-by: Ellis Tarn --- website/content/en/docs/concepts/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/content/en/docs/concepts/_index.md b/website/content/en/docs/concepts/_index.md index 4b9fb3e59e3e..2675f93740fd 100644 --- 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 %}}