[EKS] [request]: create managed nodegroups without scaling one instance when minimum is 0
- Dominant language
- Shell
- Stars
- 5.4k
- Forks
- 334
- PR merge metrics
- No merged PRs in 30d
Description
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) 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
**Tell us about your request**
allow creation of a managed nodegroup min=0, max=N without testing the nodegroup with 1 instance - just create it, but don't set desired to 1 when min=0
**Which service(s) is this request for?**
EKS
**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
if I create a managed nodegroup with all possible N vcpu instance types, then EKS creates the nodegroup, and then creates the auto scaling group and then sets desired to 1 to test it.
This doesn't really make sense as the nodegroup contains many instance types (eg. all N core). So it only tests the auto scaling group with one of the instances.
And, if this nodegroup contains only spot instances it might be that none of the instance types are currently available.
When nodegroup fails to scale up, the creation of the nodegroup fails and I have to retry until it succeeds.
This also costs (launching a 96core instance for few minutes for no reason)
**Are you currently working around this issue?**
I can not, EKS/ASG controls this.
**Additional context**
related to #724
Contributor guide
Research direction
No repository files, tests, or entry points are named. Start by reviewing related issue #724 and the described EKS managed nodegroup creation behavior; done means allowing min=0 nodegroups to be created without temporarily setting desired capacity to 1.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100