[EKS] [request]: Support Security Group Names when using Security Groups for Pods #1674
Description
Community Note
- Please vote on this issue by adding a 👍 reaction 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
We would like to be able to use Security Group names when leveraging SG for Pods functionality.
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?
At present we rebuild our AWS infrastructure on a nightly basis, we use Terraform Modules that provision RDS instances and Security Groups for granting access. At present each night when environments are rebuilt, the Security Group ID changes, we then need to update our deployment manifests for our workloads within EKS. If we could use the SecurityGroup names, we would be able to leave the workload manifests as is after rebuilding our AWS infrastructure.
Are you currently working around this issue?
We have a complex pipeline that updates our manifests and checks them into Git (as we are using GitOps)
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.)