It seems DOs Loadbalancers do not honor “externalTrafficPolicy: Local” Setting in Kubernetes Service definition. With this setting in GKE, the original client IP Adress is contained in the TCP Source IP Header. With DOs Loadbalancers, that is not the case.
How can I preserve the original client IP Adress when using SSL Passthrough (where you cannot modify the HTTP Headers and therefore X-Forwarded-For is not an option)?
spec: type: LoadBalancer externalTrafficPolicy: Local # preserves source ip ports:
- name: ambassador-plain port: 80
- name: ambassador-tls port: 443
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
There was a large release to DOKS to support auto-scaling which is now also available and it should now respect “service.spec.externalTrafficPolicy” being set to local.
I have also noticed this issue. I have set my service with type LoadBalancer and externalTrafficPolicy: Local, but the internal IP is forwarded, not the external. Setting that with NodePort works, but NodePort isn’t what most people need/want.
Hi @moisey - I have just tried this on my 1.15.4-do.0 cluster and I still do not see external IPs.
Right now the source IP is showing as 10.135.29.9 (an internal IP).
I have tried deleting and recreating the service, but that hasn’t affected it.
My service definition is here: https://github.com/andrewmichaelsmith/kubedefs/blob/master/honeytrap/honeytrap.yaml#L113
Any ideas? This is a critical feature for me, I’d rather not use Azure, but this is a blocker for this project.
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.