[EKS] [request]: Support > 100 managed node groups

[mseiwald]

Community Note

• 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

Tell us about your request Increase the current hard limit of 100 EKS managed node groups.

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? We use managed node groups to isolate different types of workloads onto their own nodes to limit the noisy neighbour effect. When using persistent volumes, it is recommended to have separate node groups per availability zone. Furthermore, during upgrades we prefer to create replacement node groups instead of upgrading the existing ones (blue green deployment). The reason we chose b/g upgrades for certain node groups is that some of our applications don't play well with draining of nodes.

This leads to the following calculation:

Number of workload types * Number of availability zones * 2 (for upgrades) = Number of needed node groups

Therefore it's not unrealistic for us to hit the 100 node group limit at some point.

Are you currently working around this issue? We currently simply need to limit ourselves in terms of how many custom node groups we can have and/or need to create additional clusters and split workloads across clusters.