autoscaler/cluster-autoscaler/cloudprovider/baiducloud
Clint Fooken 08dfc7e20f Changing deletion logic to rely on a new helper method in ClusterStateRegistry, and remove old complicated logic. Adjust the naming of the method for cloud instance deletion from NodeExists to HasInstance. 2022-11-04 17:54:05 -07:00
..
baiducloud-sdk-go Bump k/k dependencies to v1.25.0 together with go.mod go version. 2022-08-26 13:38:07 +02:00
examples CA - Cloud Provider Examples - add ability to list/watch/get namespaces 2021-08-23 15:39:38 +01:00
OWNERS Add hello2mao as an approver for baidu cloud provider 2019-05-15 13:33:19 +02:00
README.md modify README and add multiple group example 2019-11-18 15:38:50 +08:00
baiducloud_auto_scaling_groups.go Migrate to klog v2 2020-06-05 17:22:26 +02:00
baiducloud_cloud_config.go add comments && unit test 2019-09-19 11:02:49 +08:00
baiducloud_cloud_provider.go Changing deletion logic to rely on a new helper method in ClusterStateRegistry, and remove old complicated logic. Adjust the naming of the method for cloud instance deletion from NodeExists to HasInstance. 2022-11-04 17:54:05 -07:00
baiducloud_cloud_provider_test.go add comments && unit test 2019-09-19 11:02:49 +08:00
baiducloud_manager.go Migrate to klog v2 2020-06-05 17:22:26 +02:00
baiducloud_manager_test.go add comments && unit test 2019-09-19 11:02:49 +08:00

README.md

Cluster Autoscaler on BaiduCloud

The cluster autoscaler on BaiduCloud scales worker nodes within any specified autoscaling group. It will run as a Deployment in your cluster. This README will go over some of the necessary steps required to get the cluster autoscaler up and running.

Kubernetes Version

Cluster autoscaler must run on v1.8.6 or greater.

Deployment Specification

1 ASG Setup (min: 1, max: 10, ASG Name: k8s-worker-asg-1)

kubectl apply -f examples/cluster-autoscaler-one-asg.yaml

Multiple ASG Setup (min: 1, max: 10, ASG Name: k8s-worker-asg-1, min: 1, max: 10, ASG Name: k8s-worker-asg-2)

kubectl apply -f examples/cluster-autoscaler-multiple-asg.yaml

Common Notes and Gotchas:

  • 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.
  • By default, cluster autoscaler will wait 10 minutes between scale down operations, you can adjust this using the --scale-down-delay flag. E.g. --scale-down-delay=5m to decrease the scale down delay to 5 minutes.

Maintainer