Created EKS using custom AMI Launch template but nodes failed to join cluster
- 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**
What do you want us to build?
**Which service(s) is this request for?**
This could be Fargate, ECS, EKS, ECR
i created an custom ami launch template and with that launch template i created EKS node group but the nodes failed to join cluster
**Are you currently working around this issue? yes
How are you currently solving this problem?
**Additional context**
Anything else we should know?
**Attachments**
If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)
Contributor guide
Research direction
The issue names a custom AMI launch template, an EKS node group, and a node-join failure, but mentions no repository files, tests, logs, or reproduction steps. Start by clarifying the AMI, launch-template configuration, bootstrap data, and join error; done would require a reproducible diagnosis or a documented roadmap change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes
- Domain
- cloud, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100