On-demand Webinar

Run the HAProxy Kubernetes Ingress Controller in External Mode

Traditionally, connecting clients to services in Kubernetes has required multiple layers of proxies. For example, an external load balancer will route traffic to your nodes. Then, kube-proxy passes the message to the node running an ingress controller. The ingress controller then relays the message to the correct pod. Having multiple layers of proxies like this can add latency and complicates troubleshooting.

The HAProxy Kubernetes Ingress Controller now supports running as an external load balancer itself, reducing latency by cutting out other layers by routing traffic directly to the Pod.

Join our webinar to learn more about running the ingress controller in external mode.


Baptiste Assmann
Principal Solutions Architect, HAProxy Technologies

Watch the webinar

In order to provide you with the requested content, we must store and process your personal data. If you authorize us to store your personal data for this purpose, check the box below. Additionally, because of changes in the regulation of personal data, HAProxy has recently updated its Privacy Policy. HAProxy encourages you to carefully review this document. By clicking "Submit Request" below (or continuing to use the site) you confirm your agreement with this amended Privacy Policy.

Thank you! Your submission was successful.