HAProxy Enterprise Ingress Controller

I have been using HAProxy  for about a year.

My main use case for HAProxy  is mostly forwarding public traffic into internal services over a Proxmox HA cluster. I get traffic from Keepalived VIP and forward it to HAProxy, and from there to internal services. I monitor and track port 80 and 443.

I am also using HAProxy for Redis  and RabbitMQ traffic. I have three dedicated servers right now, with each server having one Redis  node and one RabbitMQ node. Based on the traffic, for example, if an API is running on host one, HAProxy forwards traffic from this API host one to host one Redis node or RabbitMQ node one, internally making them use the same host to prevent latency.

The best features HAProxy offers for my setup are easy configuration, as I don't need to set up many things; I just installed it and write configurations based on my needs. Traffic flows easily, and it's easy to manage all the internal services in one place, in one file.

The configuration is easy for me because the syntax is straightforward; it's easy to catch paths and domains. It seems simpler than NGINX , and the load balancing is very good on HAProxy. The load balancing is easy on HAProxy, and I appreciate that.

HAProxy has positively impacted my organization by making it easier for me to manage configurations. I put configuration files on the Ceph  storage shared across the whole cluster, allowing me to write my configuration, change it easily in one place, and reload it. I wrote a reload script that reloads all the configurations on all the cluster nodes, allowing them to run smoothly.

I don't know how much time I save, but it made my setup stable, which is the most positive aspect. There are months when I don't even touch it as long as I don't add a new service on my cluster.

HAProxy is very easy for me to use. I installed it easily and configured it after checking the documentation, which was clear. I wrote as described, and it worked well, but an easier desktop interface to connect to a remote server and make changes on my PC would be beneficial.

An alerting system would be better as I need to check log files if any backend is down. Integrated Telegram alerts or WhatsApp or different channels would make it better.

HAProxy is very stable.

HAProxy's scalability is easy for me as I'm using it on dedicated servers with a cluster, but I haven't used it for Kubernetes  or any other cloud platforms, so I cannot comment on that.

I was using NGINX  before switching to HAProxy.

Setting up HAProxy didn't cost anything for me.

Setting up HAProxy didn't cost anything for me.

Before choosing HAProxy, I discussed it with ChatGPT, found it convenient, tried it, tested it, and it was fine, so I didn't bother to try anything else.

My advice to others looking into using HAProxy is to dive straight into it; there's nothing to lose and many things to gain. I would rate this product an 8.