Release notes for Cluster Autoscaler 1.0.3
This commit is contained in:
parent
2589c43a61
commit
f7f2661a33
|
|
@ -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)
|
||||
|
||||
<sup>*</sup>Unless the pod has the following annotation:
|
||||
<sup>*</sup>Unless the pod has the following annotation (supported in CA 1.0.3 or later):
|
||||
```
|
||||
"cluster-autoscaler.kubernetes.io/safe-to-evict": "true"
|
||||
```
|
||||
|
|
|
|||
|
|
@ -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).
|
||||
|
|
|
|||
Loading…
Reference in New Issue