[EKS] [request]: EKS Auto Mode Windows Nodes
- 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**
Currently, EKS Auto Mode does not support Windows nodes, but Karpenter does. This request proposes adding support for Windows nodes in EKS Auto Mode.
**Which service(s) is this request for?**
EKS Auto Mode
**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
Would like to manage all nodes via the karpenter that's deployed with EKS auto mode
**Are you currently working around this issue?**
Yes standard karpenter and well as managed node groups both support windows.
Contributor guide
Research direction
No files, tests, or entry points are identified in the issue. Start by reviewing EKS Auto Mode's node support and its deployed Karpenter integration, then compare the existing Windows-node capability in standard Karpenter. Done means EKS Auto Mode can manage Windows nodes through its Karpenter deployment.
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
- 25/100