[EKS] [request]: toggleable aws-auth roleArn deletion for managed node groups
- 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**
Make toggleable aws-auth roleArn deletion for 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?**
Currently if we create a managed node group and an unmanaged set of nodes that use the same roleArn, then deletion of the managed node group will remove the roleArn that is still in use by the unmanaged nodes. This orphans the unmanaged nodes and would require the user to add the roleArn back in. It would be nice to allow infrastructure as code software like terraform or eksctl to manage it instead since it has an overall view of nodes that are deployed.
**Are you currently working around this issue?**
Manually adding the aws-auth roleArn entry back in
**Additional context**
**Attachments**
Contributor guide
Research direction
Start by reviewing the EKS managed node group deletion behavior described here, focusing on the aws-auth roleArn entry shared with unmanaged nodes. Compare how Terraform or eksctl could control this behavior, and consider the request complete when roleArn deletion can be toggled without orphaning still-active unmanaged nodes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100