Skip to content

operator: give UDP gateway listeners their own name so TCP can share the port - #53

Merged
yekta merged 1 commit into
masterfrom
chore/review-unb-465
Nov 5, 2026
Merged

yekta merged 1 commit into
masterfrom
chore/review-unb-465

Conversation

@yekta

@yekta yekta commented Nov 5, 2026

Copy link
Copy Markdown
Contributor

Every L4 Gateway listener was named l4-<nodePort>. When a service exposed TCP and UDP on the same port, the Gateway got two listeners with the same name, and the TCPRoute and UDPRoute both pointed at the same section.

  • UDP listeners are now named l4-udp-<nodePort>, and the UDPRoute's sectionName points at that listener.
  • TCP listeners still use l4-<nodePort>, so existing Gateways and TCPRoutes stay the same.

Addresses UNB-465.

Testing

  • Added TestGatewayL4TCPAndUDPOnSamePort. It builds routes for a service with TCP and UDP both on port 8388. It checks that the Gateway has an l4-8388 TCP listener and an l4-udp-8388 UDP listener, and that each route points at its own listener.

…the port

L4 listeners were all named l4-<nodePort>. So a service exposing TCP and UDP on the same port produced two Gateway listeners with the same name, and the two routes pointed at the same section.

UDP listeners are now named l4-udp-<nodePort>. TCP listeners keep their existing l4-<nodePort> name so current gateways and TCPRoutes don't change.
@yekta
yekta merged commit 2959b5b into master Nov 5, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant