-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Documentation for ProxyProtocol with AWS ELB to get Client IP #175
Comments
I saw your issue in the chat but you solved it with a Service annotation like below. Note for others, despite the discussion right now, the only allowed value is "*".
|
Closing. This example shows how it's possible to configure the ELB https://github.com/kubernetes/ingress/tree/master/examples/aws/nginx |
@aledbf your link is a 404 |
Also a 404! |
FWIW, I think this is where the aforementioned broken links would take you: |
again 404. |
@paulashbourne the deployment now is just one yaml file. |
Hi,
While attempting to get ProxyProtocol working on AWS to get Client IPs, I followed the docs and added the ProxyProtocol policy to the ELB and
use-proxy-protocol: "true"
on the nginx-ingress-controller configMap, I ran into what seemed like a brick wall and it was only after talking with @justinsb did I discover that there's an nginx-ingress-controller service annotation for that, described in kubernetes/kubernetes#24569What I was missing was this doing a string match against this constant so the ProxyProtocol policy I had on the ELB wasn't working due to being incorrectly named.
I'd be happy to submit a PR for some updates, creating the issue for anyone else who runs into this.
The text was updated successfully, but these errors were encountered: