Replies: 1 comment 2 replies
-
AFAIK it's not possible to configure it on a per port basis, but let's see if others might have more info about it. Can you not just use a separate load balancer for that? |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I use a ingress-nginx config like the following:
As you can see, I enable the PROXY Protocol to reveal the external IP of HTTP/S connections. That works.
At the same time I use the same Nginx Ingress to forward TCP traffic to a OpenVPN server.
This basically works in that the OpenVPN port reaches the pods. The problem is that there is the PROXY Protocol header in the TCP data stream (which OpenVPN does not support).
I think this is because the port is configured on the Hetzner LB to use the PROXY PROTOCOL, just like the HTTP and HTTPS ports. Manually disabling the PROXY PROTOCOL for that port in the Hetzner Cloud Console solves the problem, but of course manually configuring things in the Console is not a solution.
Is it possible to configure this so that just the 1194 port is not configured to use the PROXY PROTOCOL?
Beta Was this translation helpful? Give feedback.
All reactions