-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Open
Labels
featureNew feature or requestNew feature or requestneeds-triageIssues that need to be triagedIssues that need to be triaged
Description
Description
What problem are you trying to solve?
I’ve opened a feature request in the core Karpenter repo (kubernetes-sigs/karpenter#2590) proposing native, schedule-based “scale-to-zero” functionality for environments like QA and staging. The goal is to allow automatic, scheduled scaling of non-production environments to zero using familiar NodePool disruption schedules—centralizing lifecycle and cost control without requiring external automation.
Because this capability would be especially valuable for AWS users running ephemeral environments, I wanted to make sure AWS provider maintainers and users are aware and can add their input.
- Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
- Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
- If you are interested in working on this issue or have submitted a pull request, please leave a comment
ian-stclab, alexissellier, maurizio-scalia, dominik-walczyna-soonly-pl, marcusramberg and 3 more
Metadata
Metadata
Assignees
Labels
featureNew feature or requestNew feature or requestneeds-triageIssues that need to be triagedIssues that need to be triaged