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

Rancher 2 node template auto scaling group (ASG) support #15305

Open
clayrisser opened this issue Aug 30, 2018 · 4 comments
Open

Rancher 2 node template auto scaling group (ASG) support #15305

clayrisser opened this issue Aug 30, 2018 · 4 comments
Labels
area/node-template kind/feature Issues that represent larger new pieces of functionality, not enhancements to existing functionality

Comments

@clayrisser
Copy link

Does rancher 2 support autoscaling groups through node templates? It would be nice to be able to scale up and down from the rancher UI, but have it done through an auto scaling group. The main reason I need this is to leverage autospotting.

@dwene
Copy link

dwene commented Aug 30, 2018

👍

@loganhz loganhz added version/2.0 area/node-template kind/enhancement Issues that improve or augment existing functionality labels Oct 6, 2018
@loganhz loganhz added this to the Backlog milestone Oct 7, 2018
@loganhz loganhz added kind/feature Issues that represent larger new pieces of functionality, not enhancements to existing functionality and removed kind/enhancement Issues that improve or augment existing functionality labels Oct 23, 2018
@inglemr
Copy link

inglemr commented Mar 28, 2019

👍

1 similar comment
@BenyH
Copy link

BenyH commented Apr 4, 2019

👍

@kgeipel-retail7
Copy link

kgeipel-retail7 commented Feb 15, 2022

Are there any news or any new plans for scheduling this topic? I would be highly interested in that feature, because the kubernetes/autoscaler isn't an option for us. Our company uses Hetzner as Cloud provider and therefor we already have existing Node Templates and Pools in our Rancher System we want to reuse, k8s/autoscaler has no access to that resources, so we must maintain the pools twice and need to take care about the node setup as well, because also the rancher node driver isn't used there.

EDIT: maybe some of the Rancher team could've a look on this PR in the kubernetes/autoscaler project

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/node-template kind/feature Issues that represent larger new pieces of functionality, not enhancements to existing functionality
Projects
None yet
Development

No branches or pull requests

8 participants