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.
This comment has been deleted
For anyone using Helm, you can replace steps 1, 2 and 3 (above) with the following …
# nginx-ingress-controller-config.yaml
controller:
config:
use-forwarded-headers: "true"
compute-full-forwarded-for: "true"
use-proxy-protocol: "true"
helm install --namespace ingress-nginx --name nginx-ingress stable/nginx-ingress -f nginx-ingress-controller-config.yaml
BTW … there’s an issue with proxy protocol and the jet stack cert-manager.
See https://github.com/jetstack/cert-manager/issues/466
My only workaround is to temporarily disable proxy protocol on the load balancer (and nginx ingress config map) allowing the certificate to be issued.
kubectl edit configmap -n ingress-nginx nginx-ingress-controller
# use-proxy-protocol: "true"