[EKS] [request]: EKS Support for Transit Gateway Multicast Domain IGMPv2

[HououinKyouma8591]

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
What do you want us to build?
EKS container ability to join IGMP groups in the transit gateway multicast domain.

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?
Moving data around via UDP multicast is a common problem for many businesses that work in the low latency space, the transit gateway multicast domain that supports auto group creation with IGMPv2 was developed to deal with multicast natively in AWS without requireing expensive network overlay solutions.
However IGMPv2 requests are not detected by the transit gateway from EKS containers in pods with nodes that are forced to use IGMPv2. This functionality works fine in EC2 and ECS however.

Are you currently working around this issue?
Unable to use EKS, forced to use ECS or EC2 which is not the preferred solution.

Additional context
EC2 and ECS already support this.
Multicast seems to be used natively within Pods (but not outside them) so IGMPv2 requests out to the transit gateway are not detected.

Attachments
None