UDP support #1430
Comments
|
/assign |
|
+1 for UDP, there is a strong use in telecommunication, all data is transferred with UDP in 3G PS, 4G both FDD and TDD, also in future 5G. I think we should start the support for UDP immediateley. |
|
I'll plus one the Telecom usecase here and broaden it to IOT/m2m devices. A huge array of existing IOT and m2m protocols are using UDP. We've been writing our new IOT platform and unfortunately will not be able to utilize a service mesh because of this. |
|
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 2 weeks unless it is tagged "help wanted" or other activity occurs. Thank you for your contributions. |
|
@cmluciano Are you working on this actively? |
|
+1 for UDP support in istio . UDP is the transport layer protocol used for communication between various entities in EPC( Evolved Packet Core ) in telecom. |
|
@shalako Just confirmed some timelines on the Envoy community call today. I halted progress for a while awaiting some Envoy refactorings & Istio 1.0 priorities. I will be continuing progress on this for an alpha implementation targeted for late Q3/early Q4. |
…istio#1403) (istio#1430) Automatic merge from submit-queue. Refactor authn filter - use simple for loop to replace fancy callbacks **What this PR does / why we need it**: use simple for loop to replace fancy callbacks, for easy readability **Which issue this PR fixes** https://github.com/istio/proxy/issues/1384 **Special notes for your reviewer**: **Release note**:
|
Another use case for UDP support: https://www.eclipse.org/hono/ |
|
+1 for UDP support. Use case is DNS, NTP, Syslog and SNMP Traps. |
|
+1 for UDP |
|
+1 for UDP support. Use case is RADIUS. |
|
+1 for UDP |
|
+1 for UDP, TFTP and syslog are required for our use-case. |
|
+1 for hosting chat services like Mumble |
|
Hi, |
|
UDP +1, I need it to proxy WireGuard traffic! |
|
+1 UDP for radius server afaik Envoy 1.19 already have an UDP support |
|
+1 UDP for SNMP Traps and Syslog |
|
+1 UDP for COAP server |
|
+1 UDP for SIP and RTP |
|
+1 UDP for SCTP and PFCP |
|
+1 UDP for anything UDP |
|
Can this be locked? |
|
Hello, I have opened a draft PR #37891 for UDP support at gateways only (for the sidecars, there is additional work in terms of iptables rules, config generation as Istio uses different codepaths for gateway and sidecar config gen). Given that Envoy support for UDP is very limited (even subset routing for canary deployments is not there), it is currently a dumb UDP proxy which load balances. See the draft PR for illustrations. |
|
+1 UDP |
|
Wow, it's been five years :) It's difficult to provide features for a mesh with the simple UDP proxy in Envoy. We cannot easily enable transport security or provide peer-to-peer telemetry, and both are the expected tablestakes for uniform traffic management. The best proposal we have right now is CONNECT-UDP by @DavidSchinazi, which builds upon HTTP CONNECT tunneling and quic, generalizing the Ambient protocol for TCP with h2 CONNECT. I'll investigate the state of Envoy support, but it looks like we're close to something working. |
|
My team is working on getting CONNECT-UDP support in Envoy. I can't commit to a precise date but we expect to have it ready in early 2023. |
|
Since connect-udp is available in envoy can work begin on the istio side now? envoyproxy/envoy#27714 |
|
@emaildanwilson Sure, why not. As any other feature, this would be opt-in, off-default at first, and driven by the concrete use cases. There are some integration challenges related to tunneling in general, e.g. using a different port for tunneling breaks the network firewall policies. |
|
Is there any workaround to support udp protocol for a vpn tunnel (OpenVPN) running behind istio mesh? |
|
This is super important - blocks any QUIC traffic via any protocol. |
FWIW there is experimental support to terminate HTTP/3 at gateway (and forward as HTTP1/2): https://github.com/istio/istio/wiki/Experimental-QUIC-and-HTTP-3-support-in-Istio-gateways |
That's good too - my application is for using QUIC with other protocols so it wouldn't quite work for me. |
|
+1 for UDP |
@kyessenov commented on Thu Jan 26 2017
Proxy manager should be in charge of routing UDP traffic. There are many pieces needed for this to work:
@rshriram commented on Thu Jan 26 2017
Do we need to handle UDP now? If we only trap tcp traffic, applications can
continue to use kube proxy as is for UDP right?
Until we have a solid use case for UDP and UDP routing or mixer related
stuff, it seems pointless to bloat envoy codebase with unnecessary
complexity.
On Thu, Jan 26, 2017 at 7:18 PM Kuat [email protected] wrote:
--
~shriram
@kyessenov commented on Thu Jan 26 2017
This is not a high priority item. As of now, we're not handling UDP traffic
at all, and don't have a good use case why we should.
On Thu, Jan 26, 2017, 4:41 PM Shriram Rajagopalan [email protected]
wrote:
@rshriram commented on Mon Feb 06 2017
@moderation you had a use case right?
@moderation commented on Tue Feb 07 2017
Yes. We are interested in using Envoy as an external service proxy for a PaaS. Typically this proxy will broker HTTP connections and TCP database connections etc. There are some people accessing Kafka external from the PaaS and the authentication scheme uses Kerberos and therefore requires UDP.
Another potential use case is in the public cloud where creating an encrypted service mesh that can handle things like DNS and NTP.
It looks like Nginx supports UDP load balancing / proxying but like a lot of their functionality it is only available in the commercial Nginx Plus product.
@rshriram commented on Tue Feb 07 2017
@moderation, thanks for the use case. Will take a look at adding this
support to envoy.
On Tue, Feb 7, 2017 at 9:54 AM moderation [email protected] wrote:
--
~shriram
@drasko commented on Thu May 25 2017
+1 for UDP, needed for CoAP and LwM2M IoT scenarios.
@shalako commented on Tue Oct 31 2017
+1 for UDP support. Needed for IOT use cases; specifically LWM2M and CoAP protocols.
@kyessenov commented on Fri Aug 04 2017
Thanks for your interest. This is blocked by Envoy issue envoyproxy/envoy#492
The text was updated successfully, but these errors were encountered: