3 ms·
haproxy is able to preserve source ip by injecting proxy protocol. nginx is capable of reading proxy protocol but not injecting it. which is why haproxy is per
by sandGorgon 9y ago
haproxy is able to preserve source ip by injecting proxy protocol. nginx is capable of reading proxy protocol but not injecting it.
which is why haproxy is perfect as the ingress for your web application. Especially if you are using something like kubernetes that will use an overlay network.
unfortunately, the momentum in kubernetes is to leverage nginx as an ingress.
- mbubb 9y ago"unfortunately, the momentum in kubernetes is to leverage nginx as an ingress." Moreso than the GCP loadbalancing or the relatively new AWS transit loadbalancers?
- sandGorgon 9y agoThat is even bigger a problem for those that do bare metal deployment. You are right - k8s is fairly built out as a post cloud load balancer system. However, in the limited work happening on lb increases, it's nginx rather than haproxy.
- manigandham 9y ago> the momentum in kubernetes is to leverage nginx as an ingress. There are many different groups, Nginx in fact has their own ingress controller [1] separate from K8S nginx ingress controller. HAProxy is older and harder to deal with for L7 ingress routing as compared to Nginx. The Istio project (using Envoy) [2] is gaining speed quickly though to become a much better ingress and internal proxy. 1. https://github.com/nginxinc/kubernetes-ingress https://github.com/nginxinc/kubernetes-ingress 2. https://istio.io https://istio.io