From 28e0965eeb98954dbfe6c6ece000c69ba318e27b Mon Sep 17 00:00:00 2001 From: Jan Chaloupka Date: Mon, 17 Oct 2022 10:47:47 +0200 Subject: [PATCH] README: be more explicit about scope of the descheduler.alpha.kubernetes.io/evict annotation --- README.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/README.md b/README.md index dbf0ab857..0bc94b0cb 100644 --- a/README.md +++ b/README.md @@ -791,6 +791,9 @@ best effort pods are evicted before burstable and guaranteed pods. * All types of pods with the annotation `descheduler.alpha.kubernetes.io/evict` are eligible for eviction. This annotation is used to override checks which prevent eviction and users can select which pod is evicted. Users should know how and if the pod will be recreated. + The annotation only affects internal descheduler checks. + The anti-disruption protection provided by the [/eviction](https://kubernetes.io/docs/concepts/scheduling-eviction/api-eviction/) + subresource is still respected. * Pods with a non-nil DeletionTimestamp are not evicted by default. Setting `--v=4` or greater on the Descheduler will log all reasons why any pod is not evictable.