You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi. I have a Gateway with exactly one listener. This listener is of the protocol UDP and a UDPRoute references it to route the UDP traffic to a coredns service (similiar to the UDP Routing guide in the documentation). This works as expected, however, when I delete the UDPRoute again the routing remains active and I am still able to reach the coredns service using dig. Only the deletion of the Gateway itself stops the UDP routing.
On Gateways with more than a single UDP listener this issue does not occur.
Steps to reproduce:
Deploy envoy gateway to a cluster
Create a Gateway with a UDP listener and no other listeners on that Gateway
Create a UDPRoute to route traffic via that Gateway to the coredns service (like in the UDP Routing guide)
Use dig to confirm the proper functioning of the UDPRoute
Delete the UDPRoute
Find UDP routing still active
I use the envoy gateway v1.2.4 (envoy v1.32.2) on a v1.27 k8s cluster with the following config:
Hi. I have a
Gateway
with exactly one listener. This listener is of theprotocol
UDP and aUDPRoute
references it to route the UDP traffic to a coredns service (similiar to the UDP Routing guide in the documentation). This works as expected, however, when I delete theUDPRoute
again the routing remains active and I am still able to reach the coredns service usingdig
. Only the deletion of theGateway
itself stops the UDP routing.On
Gateway
s with more than a single UDP listener this issue does not occur.Steps to reproduce:
Gateway
with a UDP listener and no other listeners on thatGateway
UDPRoute
to route traffic via thatGateway
to the coredns service (like in the UDP Routing guide)dig
to confirm the proper functioning of theUDPRoute
UDPRoute
I use the envoy gateway v1.2.4 (envoy v1.32.2) on a v1.27 k8s cluster with the following config:
The text was updated successfully, but these errors were encountered: