diff --git a/cluster-autoscaler/FAQ.md b/cluster-autoscaler/FAQ.md index efea2757f1..e7aab6d3e5 100644 --- a/cluster-autoscaler/FAQ.md +++ b/cluster-autoscaler/FAQ.md @@ -79,7 +79,7 @@ Cluster Autoscaler decreases the size of the cluster when some nodes are consist * Pods that cannot be moved elsewhere due to various constraints (lack of resources, non-matching node selctors or affinity, matching anti-affinity, etc) -*Unless the pod has the following annotation: +*Unless the pod has the following annotation (supported in CA 1.0.3 or later): ``` "cluster-autoscaler.kubernetes.io/safe-to-evict": "true" ``` diff --git a/cluster-autoscaler/README.md b/cluster-autoscaler/README.md index 455e01d904..937775d045 100644 --- a/cluster-autoscaler/README.md +++ b/cluster-autoscaler/README.md @@ -29,6 +29,12 @@ there is a big chance that it won't work as expected. # Notable changes +CA version 1.0.3: +* Adds support for safe-to-evict annotation on pod. Pods with this annotation + can be evicted even if they don't meet other requirements for it. +* Fixes an issue when too many nodes with GPUs could be added during scale-up + (https://github.com/kubernetes/kubernetes/issues/54959). + CA Version 1.0.2: * Fixes issues with scaling node groups using GPU from 0 to 1 on GKE (https://github.com/kubernetes/autoscaler/pull/401) and AWS (https://github.com/kubernetes/autoscaler/issues/321). * Fixes a bug where goroutines performing API calls were leaking when using dynamic config on AWS (https://github.com/kubernetes/autoscaler/issues/252).