Cluster autoscaler limit scale up

[bartjanssens92]

Which component are you using?:
cluster-autoscaler

What version of the component are you using?:

Component version: 1.29.0

What k8s version are you using (kubectl version)?:

kubectl version Output

$ kubectl version
Client Version: v1.30.1
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.29.4+rke2r1

What environment is this in?:
On cloud provider rancher on Openstack.

What did you expect to happen?:
There to be a flag to set how much nodes and how fast the CA can create them, similar to spark's parameters:

spark.kubernetes.allocation.batch.size 	5 	Number of pods to launch at once in each round of executor pod allocation. 	2.3.0
spark.kubernetes.allocation.batch.delay 	1s 	Time to wait between each round of executor pod allocation. Specifying values less than 1 second may lead to excessive CPU usage on the spark driver. 

Source

The issue is that as long as there is only one spark job started it will honor these limits and allow for the Openstack API to have some breathing room but once multiple jobs are started with the same parameters it will quickly overload rancher and in turn, the Openstack API.

What happened instead?:
We did find the --max-nodes-per-scaleup flag but it does not seem intended for this use-case. Setting it does what we expected and fixes the throttle issues on the API side but it is not documented in the FAQ.md document, perhaps for this reason?

How to reproduce it (as minimally and precisely as possible):
As there is not really an error in the CA but more in the Openstack API due to rate limiting this section is empty.

Anything else we need to know?:
Thank you for all your hard work!

[kundan2707]

as this is not bug in autoscaler it should be open in cloud-provider-openstack.

[kundan2707]

/transfer cloud-provider-openstack

[zetaab]

@kundan2707 as co-lead of cloud-provider-openstack - I am not aware of autoscalers in this repository. This is now totally in incorrect repository.

/close

[k8s-ci-robot]

@zetaab: Closing this issue.

In response to this:

@kundan2707 as co-lead of cloud-provider-openstack - I am not aware of autoscalers in this repository. This is now totally in incorrect repository.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[kundan2707]

/reopen

[k8s-ci-robot]

@kundan2707: Reopened this issue.

In response to this:

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[kundan2707]

transferring again to autoscaler as openStack API donot belongs to this repo

[kundan2707]

/transfer autoscaler

[adrianmoisey]

/area cluster-autoscaler