Skip to content
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

Support for proxy protocol v2 #675

Open
UltraInstinct14 opened this issue May 13, 2024 · 1 comment
Open

Support for proxy protocol v2 #675

UltraInstinct14 opened this issue May 13, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@UltraInstinct14
Copy link
Contributor

Is your feature request related to a problem? Please describe.
In many NAT nodes used by loxilb, the original sourceIP gets obfuscated at the endpoint. It might result in problem of accounting various things related to the original source such as abuse, DDOS attacks or to keep simple statistical counts.

Describe the solution you'd like
loxilb needs to implement proxy protocol v2. Currently many web-servers already support it

Describe alternatives you've considered
N/A

Additional context
https://www.haproxy.org/download/1.8/doc/proxy-protocol.txt

@UltraInstinct14 UltraInstinct14 added the enhancement New feature or request label May 13, 2024
@6547709
Copy link

6547709 commented Nov 4, 2024

I also need this feature;
Background:
I have always used the architecture of deploying LoadBalancer outside the cluster, which has a clear architecture, short path (LB->PodIP), and better performance (adjusting virtual machine/bare metal configuration). When I use TCP service or Ingress, the source IP (one-arm/FullNAT) cannot be correctly identified;
Requirement:
If LoxiLB can support Proxy protocol V2, these problems can be solved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants