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
Is this a BUG REPORT or FEATURE REQUEST? (choose one): FEATURE REQUEST
If this is a FEATURE REQUEST, please:
"proxy_responses" value is configurable with udp/tcp configmaps (annotation?)
Currently this value is hard-coded in the nginx.conf template file
Reasoning:
I'm currently trying to use ingress-nginx to expose a udp application (teamspeak) with a long-living udp connection cycle. I can use nc to see the service is exposed
$ nc -v -u -z -w 3 10.1.101.10 9987
$ Connection to 10.1.101.10 9987 port [udp/*] succeeded!
Trying to use the exposed port to reach the application acces_logs show a udp entry, but the application doesn't "connect":
i see that the feature request has been solved. However i am currently trying to accomplish the same as you, @NinjaBanjo . Could you please let me know if you managed to get teamspeak working with this method? Even though the server "works", I am experiencing a lot of packetloss when using the nginx udp ingress for it which makes it unusable. thank you
Is this a BUG REPORT or FEATURE REQUEST? (choose one): FEATURE REQUEST
If this is a FEATURE REQUEST, please:
Currently this value is hard-coded in the nginx.conf template file
Reasoning:
I'm currently trying to use ingress-nginx to expose a udp application (teamspeak) with a long-living udp connection cycle. I can use nc to see the service is exposed
Trying to use the exposed port to reach the application acces_logs show a udp entry, but the application doesn't "connect":
The text was updated successfully, but these errors were encountered: