Here is a quick introduction to HAProxy as Egress Kubernetes. Our Server Management Support team is here to lend a hand with your queries and issues.

An Introduction to HAProxy as Kubernetes Egress Controller

HAProxy, short for High Availability Proxy, is a well-known open-source software TCP/HTTP Load Balancer. In other words, it is a proxying solution that can run on Linux, FreeBSD as well as macOS. It is used widely to boost the performance and reliability of a server environment. This is done by distributing the workload across different servers.

In Kubernetes egress, unlike ingress, the traffic is handled at a networking level. Furthermore, we can add egress behavior to the network implementation if a service mesh is used.

According to our experts, adding HAProxy as Kubernetes Egress Controller will result in a few changes,  For instance, we will not run into ErrorPortlocation any longer. Additionally, request duration goes down by almost 10%.

In order to use the HAProxy Kubernetes Ingress controller as an Egress Controller, we have to use the Ingress Kubernetes resources as Egress. This is done to define the domains managed by the Controller.

Once done, we will be able to send requests:

curl -H "host: app1.example.com" https://haproxy-egress.default.svc.cluster.local/health

Although HAProxy resolved domain names at boot time by default, we can configure it to resolve at run time with this configuration snippet in the Egress Controller configuration.

Let us know in the comments if you would like further help from our experts in order to use HAProxy as a Kubernetes Egress Controller.

[Need assistance with a different issue? Our team is available 24/7.]

Conclusion

In conclusion, our Support Engineers introduced us to use the HAProxy Kubernetes Ingress controller as an Egress Controller.