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
NLBs managed by EKS auto mode clusters should support TCP_UDP Listeners when the service defines a TCP and UDP port on the same port number. This is already possible in the upstream AWS LBC since v2.13.0.
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?
For some applications there's a hard requirement to support both TCP and UDP using the same port number.
Are you currently working around this issue?
Using TargetGroupBinding with a NLB/Target Group managed outside of EKS.
Community Note
Tell us about your request
NLBs managed by EKS auto mode clusters should support TCP_UDP Listeners when the service defines a TCP and UDP port on the same port number. This is already possible in the upstream AWS LBC since v2.13.0.
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?
For some applications there's a hard requirement to support both TCP and UDP using the same port number.
Are you currently working around this issue?
Using TargetGroupBinding with a NLB/Target Group managed outside of EKS.