-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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] EKSCTL can create scheduled scaling rules #5524
Comments
Plus 1 on this - having the ability to apply scheduled scaling rules within eksctl can allow us to program scaledown events for dev clusters to save money. |
Hi all, any updates on this? Applying it manually after cluster creation is not an effective manner. It would save us a lot of money and overhead |
Hi, why don't you use cluster autoscaler https://github.com/kubernetes/autoscaler? You can still set a maximum in the ASG group. |
Hi @bcoromina the |
If you want to force instance to 0 at specific time and ignore the possible activity that makes sense. |
Hey @Himangini |
@hassaanakram Ty for showing interest in contributing to |
Hi @Himangini I have some questions, but before that some context: Scheduled Scaling action is a property of the Auto scaling group and therefore the ASG must exist before Scheduled Scaling rules may be applied. Therefore, the Scheduled Scaling resource cannot be added to the NodeGroup CloudFormation template and must come after the NodeGroup ASG creation. I can see two ways to do that (after node group creation)
I am not really sure which is the idiomatic way to move forward here. Your input will be appreciated. Thanks! Draft PR for ref: #6732 |
What feature/behavior/change do you want?
I would like to be able to control
Auto Scaling Groups
created byEKS
witheksctl
. We use aScheduled Scaling
a part ofASG
to scale down the clusters after work hours to reduce cost It would be nice if we could include the scaling rules inside of the yaml.Why do you want this feature?
It would be able to track these rules as infrastructure as code.
The text was updated successfully, but these errors were encountered: