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 Team,
I'm experimenting with the kong ingress controller v2.8.2 to route UDP traffic to a backend service.
I have a client which sends every request from the same source IP and port to the Kong service (type: LB). The request is then routed to my backend service with a source IP and a port of the pod running the kong-proxy.
But if the client stays idle for more than 60 seconds, the kong-proxy is using a new port to route the request to the backend. Is there a way to configure this, so that the requests from the same client is always routed using the same source port?
Or is it possible to enable transparent proxy for UDP traffic?
Any help in this regard is highly appreciated. Thanks in advance.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi Team,
I'm experimenting with the kong ingress controller v2.8.2 to route UDP traffic to a backend service.
I have a client which sends every request from the same source IP and port to the Kong service (type: LB). The request is then routed to my backend service with a source IP and a port of the pod running the kong-proxy.
But if the client stays idle for more than 60 seconds, the kong-proxy is using a new port to route the request to the backend. Is there a way to configure this, so that the requests from the same client is always routed using the same source port?
Or is it possible to enable transparent proxy for UDP traffic?
Any help in this regard is highly appreciated. Thanks in advance.
Beta Was this translation helpful? Give feedback.
All reactions