Support UDP with AWS NLB

[kirrmann]

What happened:
Error creating load balancer (will retry): failed to ensure load balancer for service default/test: Only TCP LoadBalancer is supported for AWS ELB

What you expected to happen: kubernetes creating an AWS NLB for UDP

How to reproduce it (as minimally and precisely as possible): Create service with annotation service.beta.kubernetes.io/aws-load-balancer-type: nlb and port with protocol: UDP

Anything else we need to know?:
AWS recently announced that UDP is available within their NLB https://aws.amazon.com/de/blogs/aws/new-udp-load-balancing-for-network-load-balancer/

Environment:

• Kubernetes version (use kubectl version): 1.11.9
• Cloud provider or hardware configuration: AWS

[justinsb]

/sig aws

[justinsb]

/kind feature

[randomvariable]

/remove-kind bug

[mcrute]

/milestone v1.16

[k8s-ci-robot]

@mcrute: You must be a member of the kubernetes/milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your and have them propose you as an additional delegate for this responsibility.

In response to this:

/milestone v1.16

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[justinsb]

/milestone v1.16

[bhks]

I am taking up this Feature Development.

How can this be assigned to me?

[RainbowMango]

/assign @bhagwat070919

[Kiranjith83]

+1

[jkennedyOM]

+1 I am experiencing the same issue. NLB also supports UDP_TCP type, any service using service.beta.kubernetes.io/aws-load-balancer-type: "nlb" should be able to mix TCP and UDP port configs.

[a7i]

@bhagwat070919 Any progress? I can collaborate on this, if you need a hand.

[OMamurphy]

+1

[michael-c-jones]

+1

On Thu, Jul 18, 2019 at 12:58 Adam Murphy ***@***.***> wrote: +1 — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#79523?email_source=notifications&email_token=AE4S5B6RCE3CNK7SYSOTAWLQACVN5A5CNFSM4H4EQRR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2JJENA#issuecomment-512922164>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AE4S5B5GRYCWTGT6SWR46EDQACVN5ANCNFSM4H4EQRRQ> .

-- -- Michael Jones [email protected]

[klamontagne-om]

+1

[owenthereal]

I just ran into this. Any updates?

[owenthereal]

Attempting to fix it with #80394

[mihyonq]

+1

[skonjarla]

+1

[DennisR73]

+1

[silesmo]

+1

[rverma-jm]

+1

[smourapina]

Hello @mmerrill3, @kirrmann, @pjryan93 !
Bug Triage team here for the 1.18 release. This is a friendly reminder that code freeze is scheduled for 5 March, which is a few weeks from now. Is this issue still intended for milestone 1.18? Thanks in advance!

[smourapina]

C/O @kubernetes/sig-cloud-provider-admins:
Code freeze for release 1.18 is starting in 5 March (less than 1 week from now) and we want to ensure that each issue has a chance to be finished on time. Is this still on track for this deadline?

[smourapina]

/remove-kind bug

[edobry]

Is there any work remaining to be done on this? Willing to contribute if so, would really love to see this make it into 1.18!

[smourapina]

Thanks for the reply @edobry! This has been a long running issue, and given that there has not been any recent activity, would it make more sense to once again move the milestone? We are 2 days away from code freeze (5 March).

[kevinresol]

Thanks for the reply @edobry! This has been a long running issue, and given that there has not been any recent activity, would it make more sense to once again move the milestone? We are 2 days away from code freeze (5 March).

I wonder what "activity" you are expecting.

[smourapina]

We are now in code freeze for 1.18, so I am moving this to the next milestone.
/milestone v1.19

[IkiM0no]

We are now in code freeze for 1.18, so I am moving this to the next milestone.
/milestone v1.19

Hello, as of now, I see milestone v1.19 is 65% completed.
May we please have an update on estimated release date of UDP support for AWS NLB?

[kevinresol]

People have been trying to be constructive here. But the team doesn't even try to tell us what is pending. Sad.

[PHameete]

Would also love to see this feature for EKS - and am willing to help out. Even if we could get it in 1.19 it would still take a long time to become available in EKS (which is currently at 1.15). So the sooner we can start work on this - the better :-)

[royyeah]

+1 Also hope we could get in 1.19 and happy to help out!

[batmac]

any update on this pretty please ?

[guruprasadgvmf]

whats the update here?

[TBBle]

From what I can see, the main issues that remain unresolved since the first PR last year:

• Different protocols in the same Service definition with type=LoadBalancer enhancements#1438 is still pending if you need a service that supports both TCP and UDP, e.g., DNS. DNS is also a more-complicated example because it supports TCP and UDP on the same port number, and that'll need more refactoring here, as AWS treats that as a single multi-protocol target. Edit: To be clear, not really a blocker for UDP support, but it's been raised in the discussion earlier.
• AWS NLB can only do TCP-based health checks (including HTTP and HTTPS), so your service needs to have a health-check TCP port listening. Current PRs silently assume it's on the same port number as the UDP service you're advertising. If you're using externalTrafficPolicy: Local, then it'll use the health check from healthCheckNodePort instead anyway. So this is probably only an issue for LoadBalancer Services with externalTrafficPolicy: Cluster set.

See "Things to know" on the original announcement blog post for NLB UDP support.