-
Notifications
You must be signed in to change notification settings - Fork 200
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Used proxy-protocol for TCP Service #318
Comments
Hi. Do you have any news about this? Possible or not? If not, in a later release? Thanks. |
Hi @tili41, Currently this is not available on TCP services. We could plan it for a future release. |
I think we better enable config-snippets for TCP frontends, this way you can add whatever configuration you want. |
Hi all! Any news on making TCP frontends accept proxy-protocol? In the annotations page, the only frontend relevant option is |
Any update on this? Or an example on how to enable accept-proxy on the frontend? |
Also interested in an easy way how to enable proxy for other frontends (e.g., stats). |
Hi, we have an external HAProxy load-balancer upstream of the K8s cluster.
We have enabled the proxy-protocol to be able to whitelist the ip allowed to connect to the different services managed by HAProxy Controller. It works well for HTTPS services.
However, it doesn't seem possible to enable the proxy-protocol for TCP services.
Without the proxy-protocol, I do not really have the interest to have whitelists for TCP services (we manage this via the Service backend-config-snippet annotation).
To be clear, we don't want to enable proxy-protocol for the backend servers but only for the frontend (Ingress Controller).
Any idea? Thank you for your help.
The text was updated successfully, but these errors were encountered: