-
Notifications
You must be signed in to change notification settings - Fork 295
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
[Feature] Support for changing scheduler configuration #3532
Comments
@EppO was there any workaround for this feature? |
we are facing the same issue there, when using cluster autoscaler, the default one doesn't works very well because new coming pod are get allocated to all the node with less utilization , this cause a waste of resource. can we expect to support add support for |
Are there any plans to expose |
We have added support for scheduler configuration to our roadmap as planned/committed. |
Is your feature request related to a problem? Please describe.
When trying to trigger down scaling of under utilized nodes, default kubernetes scheduler strategy
LeastAllocated
makes it difficult to achieve.Describe the solution you'd like
Allow the AKS admin to change the
KubeSchedulerConfiguration
's default settings like described here: https://kubernetes.io/docs/reference/scheduling/config/Describe alternatives you've considered
I tried to use descheduler but it fell short for the same reason.
Additional context
The
MostAllocated
strategy scores the nodes based on the utilization of resources, favoring the ones with higher allocation, maximizing usage of busiest nodes allowing the autoscaler to downscale under utilized nodes.The
RequestedToCapacityRatio
strategy allows the users to specify the resources along with weights for each resource to score nodes based on the request to capacity ratio. This allows users to bin pack extended resources by using appropriate parameters to improve the utilization of scarce resources in large clusters. It favors nodes according to a configured function of the allocated resourcesThe text was updated successfully, but these errors were encountered: