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

[Feature Request] Autoscaling at nodepool level #1866

Open
Shaybs opened this issue Sep 22, 2020 · 4 comments
Open

[Feature Request] Autoscaling at nodepool level #1866

Shaybs opened this issue Sep 22, 2020 · 4 comments
Assignees

Comments

@Shaybs
Copy link

Shaybs commented Sep 22, 2020

Hi Microsoft team,

So our company is using EKS and AKS at the moment. However, we have an architecture where we are using two completely different nodepools. We are now seeking to make the nodepools autoscale. However, the scale-down-utilization-threshold is set at the cluster level. Whereas we require different settings for scaling down thresholds because the lower end of the nodepools' utilisation is very different (i.e. 0.15 for one nodepool and over 0.4 for the other) for more efficiency. I also think this feature would be incredibly beneficial to other users/companies.

Sincerely yours,
Shuaib

@ghost ghost added the triage label Sep 22, 2020
@ghost
Copy link

ghost commented Sep 22, 2020

Hi Shaybs, AKS bot here 👋
Thank you for posting on the AKS Repo, I'll do my best to get a kind human from the AKS team to assist you.

I might be just a bot, but I'm told my suggestions are normally quite good, as such:

  1. If this case is urgent, please open a Support Request so that our 24/7 support team may help you faster.
  2. Please abide by the AKS repo Guidelines and Code of Conduct.
  3. If you're having an issue, could it be described on the AKS Troubleshooting guides or AKS Diagnostics?
  4. Make sure your subscribed to the AKS Release Notes to keep up to date with all that's new on AKS.
  5. Make sure there isn't a duplicate of this issue already reported. If there is, feel free to close this one and '+1' the existing issue.
  6. If you have a question, do take a look at our AKS FAQ. We place the most common ones there!

@ghost ghost removed the triage label Sep 22, 2020
@ghost ghost added the action-required label Oct 17, 2020
@ghost
Copy link

ghost commented Oct 22, 2020

Action required from @Azure/aks-pm

@ghost ghost added the Needs Attention 👋 Issues needs attention/assignee/owner label Oct 22, 2020
@palma21 palma21 added feature-request Requested Features Feedback General feedback labels Feb 23, 2021
@ghost ghost removed action-required Needs Attention 👋 Issues needs attention/assignee/owner labels Feb 23, 2021
@Azure Azure deleted a comment Feb 23, 2021
@Azure Azure deleted a comment Feb 23, 2021
@Azure Azure deleted a comment Feb 23, 2021
@Azure Azure deleted a comment Feb 23, 2021
@Azure Azure deleted a comment Feb 23, 2021
@Azure Azure deleted a comment Feb 23, 2021
@Azure Azure deleted a comment Feb 23, 2021
@Azure Azure deleted a comment Feb 23, 2021
@palma21
Copy link
Member

palma21 commented Feb 23, 2021

Added the feature request tracker, we'd love to, unfortunately the upstream Cluster Autoscaler project doesn't have that concept and the settings/profile are done at the component level which affect all targeted node groups, we are however working upstream to the community to get this capability and architecture change considered upstream.

@Shaybs
Copy link
Author

Shaybs commented Oct 1, 2021

@palma21 Thanks, we'd deeply appreciate the addition of the feature as would many other AKS users.

@ghost ghost added the action-required label Mar 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants