Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add more autoscaling options that can be defined per VM Scale Set #6935

Open
marcoboffi opened this issue Jun 18, 2024 · 0 comments
Open

Add more autoscaling options that can be defined per VM Scale Set #6935

marcoboffi opened this issue Jun 18, 2024 · 0 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@marcoboffi
Copy link

Cluster autoscaler for Azure
Is your feature request designed to solve a problem? If so describe the problem this feature should solve.:

Currently it is only possible to define certain autoscaling options for the VM Scale Set using tags [link].
Having dedicated nodepools for specific workloads would be very useful to be able to differentiate as many parameters as possible for each nodepool.
In some cases I am forced to dispense with the autoscaler (scaling manually after alerts), while in other cases I have to execute the workload on different clusters.

Describe the solution you'd like.:

Add more autoscaling options that I can override to differentiate vmss autoscale behaviour for each nodepool.
In particular I'm interested to following parameters:

  • new_pod_scale_up_delay
  • max_unready_percentage
  • max_unready_nodes
  • scale_down_delay_after_add
  • scale_down_delay_after_delete
  • scale_down_delay_after_failure

Describe any alternative solutions you've considered.:

Additional context.:

@marcoboffi marcoboffi added the kind/feature Categorizes issue or PR as related to a new feature. label Jun 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

1 participant