haproxy_2_2_ama_webinar

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.

Speaker: Baptiste Assmann

REGISTER NOW

SHARE THIS ARTICLE