Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

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!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
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.