Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Support DTLS and UDP routing #239

Open
fire opened this issue Sep 10, 2019 · 21 comments
Open

Support DTLS and UDP routing #239

fire opened this issue Sep 10, 2019 · 21 comments
Labels
kind/feature New feature triage/accepted The issue was reviewed and is complete enough to start working on it

Comments

@fire
Copy link

fire commented Sep 10, 2019

Summary

Support DTLS or UDP routing? This is useful for game server hosting that uses kuma as a load balancer and for things like internet of things endpoints.

Steps To Reproduce

Use kuma.

Additional Details & Logs
@jakubdyszkiewicz
Copy link
Contributor

At the moment Envoy itself (which Kuma use as a Data Plane) does not support UDP envoyproxy/envoy#492
As soon as this is implemented we can take a look at supporting it in Kuma.

@fire
Copy link
Author

fire commented Dec 7, 2019

Ping. Status changed on the 492 issue.

@danielle-mustillo danielle-mustillo mentioned this issue Mar 31, 2020
Open
@rbtcollins
Copy link

Envoy now supports UDP and QUIC from what I can tell.

@jakubdyszkiewicz
Copy link
Contributor

That's true. It should be pretty straightforward to implement.
We need to add support for another protocol in protocol tag (just like we did recently for HTTP2 and gRPC in progress).

Then instead of TCPProxy we need to set UDPProxy filter. Also listener's socket should be opened as UDP.
When generating outbound listeners we also need to look if protocol is UDP and set proper filter and socket type

Limitations

  • TrafficRoute won't work since there is no subset loadbalcning for UDP Proxy filter
  • Cross cluster communication might be broken, mTLS should work with UDP, but Ingress assumes TCP
  • You need to find Gateway (entry point to the mesh) that supports UDP

@nickolaev
Copy link
Contributor

@tharun208 will check this one.

tharun208 referenced this issue in tharun208/kuma Aug 5, 2020
@tharun208
feat(kuma-cp) Support for udp
6a15485 
Fixes #239

Signed-off-by: Tharun <[email protected]>
@tharun208 tharun208 mentioned this issue Aug 5, 2020
Closed
1 task
tharun208 referenced this issue in tharun208/kuma Aug 5, 2020
@tharun208
feat(kuma-cp) Support for udp
ad9fb61 
Fixes #239

Signed-off-by: Tharun <[email protected]>
tharun208 referenced this issue in tharun208/kuma Aug 5, 2020
@tharun208
feat(kuma-cp) Support for udp
61eb000 
Fixes #239

Signed-off-by: Tharun <[email protected]>
tharun208 referenced this issue in tharun208/kuma Aug 14, 2020
@tharun208
feat(kuma-cp) Support for udp
272f4f8 
Fixes #239

Signed-off-by: Tharun <[email protected]>
tharun208 referenced this issue in tharun208/kuma Jan 7, 2021
@tharun208
feat(kuma-cp) Support for udp
8d4145c 
Fixes #239

Signed-off-by: Tharun <[email protected]>
@lahabana lahabana added kind/feature New feature area/adoption Likely to cause problem to new comers and removed feature-request area/adoption Likely to cause problem to new comers labels Nov 22, 2021
@github-actions
Copy link
Contributor

This issue was inactive for 30 days it will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant please comment on it promptly or attend the next triage meeting.

@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Dec 27, 2021
@mskarbek
Copy link

It is still relevant.

@lahabana lahabana removed the triage/stale Inactive for some time. It will be triaged again label Apr 14, 2022
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label May 15, 2022
@github-actions
Copy link
Contributor

This issue was inactive for 30 days it will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant please comment on it promptly or attend the next triage meeting.

@lahabana lahabana added triage/pending This issue will be looked at on the next triage meeting and removed triage/stale Inactive for some time. It will be triaged again labels May 17, 2022
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Jun 17, 2022
@github-actions
Copy link
Contributor

This issue was inactive for 30 days it will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant please comment on it promptly or attend the next triage meeting.

@mskarbek
Copy link

It is still relevant.

@jakubdyszkiewicz jakubdyszkiewicz added triage/accepted The issue was reviewed and is complete enough to start working on it and removed triage/pending This issue will be looked at on the next triage meeting labels Sep 7, 2022
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Dec 7, 2022
@github-actions
Copy link
Contributor

github-actions bot commented Dec 7, 2022

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@mskarbek
Copy link

mskarbek commented Dec 7, 2022

It is still relevant.

@michaelbeaumont michaelbeaumont removed the triage/stale Inactive for some time. It will be triaged again label Dec 7, 2022
@jakubdyszkiewicz jakubdyszkiewicz mentioned this issue Feb 27, 2023
Closed
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Mar 8, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Mar 8, 2023

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@lukidzi lukidzi removed the triage/stale Inactive for some time. It will be triaged again label Mar 14, 2023
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Jun 13, 2023
@github-actions
Copy link
Contributor

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@bartsmykla bartsmykla removed the triage/stale Inactive for some time. It will be triaged again label Jun 22, 2023
@github-actions
Copy link
Contributor

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Sep 21, 2023
@lobkovilya lobkovilya removed the triage/stale Inactive for some time. It will be triaged again label Sep 27, 2023
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Dec 27, 2023
@github-actions GitHub Actions
Copy link
Contributor

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@michaelbeaumont michaelbeaumont removed the triage/stale Inactive for some time. It will be triaged again label Jan 2, 2024
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Apr 2, 2024
@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Apr 2, 2024

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@mskarbek
Copy link

mskarbek commented Apr 2, 2024

This is still a thing. It would be useful with https://gateway.envoyproxy.io/v0.3.0/user/udp-routing/.

@slonka
Copy link
Contributor

slonka commented Apr 2, 2024

@mskarbek - I don't think this is currently on our roadmap but if you'd like to implement this we will help you with the PR. FYI @lahabana @jakubdyszkiewicz

@slonka slonka removed the triage/stale Inactive for some time. It will be triaged again label Apr 2, 2024
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Jul 3, 2024
@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Jul 3, 2024

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@jakubdyszkiewicz jakubdyszkiewicz removed the triage/stale Inactive for some time. It will be triaged again label Jul 10, 2024
@github-actions GitHub Actions
Copy link
Contributor

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Oct 10, 2024
@lukidzi lukidzi removed the triage/stale Inactive for some time. It will be triaged again label Oct 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature New feature triage/accepted The issue was reviewed and is complete enough to start working on it
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat(kuma-cp) Support for udp tharun208/kuma