aws / aws/containers-roadmap

[EKS] [request]: Managed Node Group and Launch template with instance type

Open
#1,352 0 comments 0 reactions 0 assignees View on GitHub
EKS EKS Managed Nodes Proposed
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 to have launch template with instance type used in node group with list of instance types.

**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?**
Was trying to have a node group having good selection of burstable instance types without being hit by CPU credits limit.

Usually when using launch template with ASG you can put an instance type in template and then put list of instance types in the ASG it self which uses the template. Since for some reason it is not allowed to both put a single instance in launch template and list of instance types in managed node group which uses this launch template, it is not possible to have T2 instances with unlimited CPU credits. The CPU credits definition seems to be discarded when not having any T2/T3 instance type in template.

**Are you currently working around this issue?**
Using only T3 which has unlimited credits by default.

Contributor guide

Open the contributing guide

Research direction

Start with issue #1352 and its description of EKS managed node groups, launch templates, Auto Scaling instance-type lists, and T2/T3 CPU-credit behavior. No repository files or tests are identified in the issue; done would mean defining and implementing support for the requested instance-type combination, with validation of the resulting node-group behavior.

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
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.