[EKS] [request]: Allow EKS UI to attached Custom Security groups along with Cluster Security group.
- 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?
A feature in EKS UI to add additional security groups to managed nodegroups instead of using [Custom Launch template](https://docs.aws.amazon.com/eks/latest/userguide/launch-templates.html#launch-template-security-groups) as mentioned in [issue 609](https://github.com/aws/containers-roadmap/issues/609)
**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?**
Instead of creating custom launch template and launching security groups creating them directly from EKS UI will be more cleaner way to add new security groups to the managed worker nodes.
Contributor guide
Research direction
The issue names no repository files, tests, or entry points. Start by reviewing the EKS UI, managed node groups, and linked custom launch-template documentation; done means the UI can add custom security groups alongside the cluster security group without requiring a custom launch template.
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