But you need your LB to use it too, or requests will fail. So it depends on 
what load balancer you are using.

On Jan 10, 2018, at 2:52 PM, John Belamaric 
<jbelama...@infoblox.com<mailto:jbelama...@infoblox.com>> wrote:

Sorry, you don’t need to manually do that. I should have sent you to this page 
instead:

https://github.com/kubernetes/ingress-nginx/blob/master/docs/user-guide/configmap.md#use-proxy-protocol

John

On Jan 10, 2018, at 2:18 PM, bg 
<griffin...@gmail.com<mailto:griffin...@gmail.com>> wrote:

Thanks! Re: Step 2:

In the set_real_ip_from directive, specify the IP address or the CIDR range of 
addresses of the TCP proxy or load balancer:

Would that be the external or the cluster ip of my load balancer? And how I dow 
I determine the CIDR block? (Sorry, this is new to me).


On Wednesday, January 10, 2018 at 5:10:08 PM UTC-5, John Belamaric wrote:
Your load balancer needs to support the proxy protocol:





https://www.nginx.com/resources/admin-guide/proxy-protocol/





John






On Jan 10, 2018, at 1:55 PM, bg <griff...@gmail.com<http://gmail.com>> wrote:





I have this set up



Load Balancer > Ingress Controller (nginx) -> Service -> Deployment (nginx).



The nginx deployment is logging `$remote_addr`and `$http_x_forwarded_for`, but 
both seem to be internal ip address. Any ideas on how I can preserve the 
client's IP?



I set the LoadBalancer's externalTrafficPolicy to Local like this:



kubectl patch svc api-lb -p '{"spec":{"externalTrafficPolicy":"Local"}}'



and verified that by running `kubectl describe svc api-lb` and saw this:



External Traffic Policy:  Local



Thanks in advance!



--

You received this message because you are subscribed to the Google Groups 
"Kubernetes user discussion and Q&A" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to
kubernetes-use...@googlegroups.com<http://googlegroups.com>.

To post to this group, send email to
kuberne...@googlegroups.com<http://googlegroups.com>.

Visit this group at
https://groups.google.com/group/kubernetes-users.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups 
"Kubernetes user discussion and Q&A" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
kubernetes-users+unsubscr...@googlegroups.com<mailto:kubernetes-users+unsubscr...@googlegroups.com>.
To post to this group, send email to 
kubernetes-users@googlegroups.com<mailto:kubernetes-users@googlegroups.com>.
Visit this group at https://groups.google.com/group/kubernetes-users.
For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to the Google Groups 
"Kubernetes user discussion and Q&A" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
kubernetes-users+unsubscr...@googlegroups.com<mailto:kubernetes-users+unsubscr...@googlegroups.com>.
To post to this group, send email to 
kubernetes-users@googlegroups.com<mailto:kubernetes-users@googlegroups.com>.
Visit this group at https://groups.google.com/group/kubernetes-users.
For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Kubernetes user discussion and Q&A" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to kubernetes-users+unsubscr...@googlegroups.com.
To post to this group, send email to kubernetes-users@googlegroups.com.
Visit this group at https://groups.google.com/group/kubernetes-users.
For more options, visit https://groups.google.com/d/optout.

Reply via email to