kubernetes
/
autoscaler
mirror of https://github.com/kubernetes/autoscaler.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #6192 from dumlutimuralp/patch-1 

Removed node drainer, kept node termination handler
This commit is contained in:
Kubernetes Prow Robot 2023-11-16 16:46:36 +01:00 committed by GitHub
parent 82f85c273d 0dd7b86602
commit f7b8072f1c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
cluster-autoscaler/cloudprovider/aws/README.md
View File

@ -496,11 +496,8 @@ Please note: it is also possible to mount the cloud config file from host:
enabled, which means it will actively work to balance the number of instances
between AZs, and possibly terminate instances. If your applications could be
impacted from sudden termination, you can either suspend the AZRebalance
feature, or use a tool for automatic draining upon ASG scale-in such as the
[k8s-node-drainer](https://github.com/aws-samples/amazon-k8s-node-drainer). The
[AWS Node Termination
Handler](https://github.com/aws/aws-node-termination-handler/issues/95) will
also support this use-case in the future.
feature, or use a tool for automatic draining upon ASG scale-in such as the [AWS Node Termination
Handler](https://github.com/aws/aws-node-termination-handler/).
- By default, cluster autoscaler will not terminate nodes running pods in the
kube-system namespace. You can override this default behaviour by passing in
the `--skip-nodes-with-system-pods=false` flag.