-
Notifications
You must be signed in to change notification settings - Fork 590
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.
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
Add UDPRoute implementation #2363
Conversation
d21967e
to
be273eb
Compare
be273eb
to
4ffbc1c
Compare
4ffbc1c
to
6a77cda
Compare
With #2087 (comment), most questions are relegated to either after experimental features become stable or until after changes to backendRef handling solidify, so this should be good to go. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like most of this is copy/pasted. I may be forgetting something: what happened to the conversation about using a generator for these?
What this PR does / why we need it:
Adds a UDPRoute controller, UDPRoute parser code, and integration test.
Which issue this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close that issue when PR gets merged): fixes #2087Special notes for your reviewer:
See #2087 (comment) for some of the design considerations and information on limitations (namely not being able to control the route destination port).
PR Readiness Checklist:
Complete these before marking the PR as
ready to review
:CHANGELOG.md
release notes have been updated to reflect any significant (and particularly user-facing) changes introduced by this PR