HAProxy 2.1: What's New, Release History & Support Lifecycle

What Is New in HAProxy 2.1

HAProxy 2.1 introduces significant enhancements in observability, security, and dynamic configuration. This release focuses on making the load balancer more transparent and easier to manage at scale.

How does HTTPS logging improve troubleshooting?

You can now log directly over HTTPS, which secures your log data in transit. This is a big deal for compliance and prevents sensitive data from being exposed on the wire. It integrates with services like Splunk and Elasticsearch without needing a separate log shipper.

In practice, you configure it with a log line that specifies an HTTPS endpoint. The load balancer handles the TLS connection, making your logging pipeline both simpler and more secure from end to end.

What's the deal with dynamic SSL certificates?

This feature lets you load new SSL certificates on the fly without a reload. You use the Runtime API to add or update certificates, which is perfect for large-scale environments with thousands of domains.

This matters because it eliminates service interruption during certificate rotations. You can automate cert updates from an ACME client like Certbot, making your infrastructure more resilient and easier to maintain.

Can HAProxy forward logs to a remote server?

Yes, the new Log Forwarding feature acts as a built-in syslog client. It can send logs to multiple destinations simultaneously, which is great for redundancy or sending data to different analysis tools.

You define a log forward section in your configuration and then reference it from your frontends and backends. This separates the logging logic from the proxy logic, giving you more flexibility in how you handle observability data.

How is the built-in Prometheus exporter used?

A new stats frontend exposes metrics in the Prometheus format natively. You just point Prometheus to the HAProxy stats URI, and it scrapes the data without needing any exporters or converters.

This simplifies your monitoring stack significantly. You get immediate insight into key metrics like request rates, error codes, and backend health, all formatted correctly for Prometheus.

What performance gains were made with caching?

The HTTP cache now supports conditional requests (If-Modified-Since). This means HAProxy can serve a 304 Not Modified response without hitting the origin server, reducing backend load and improving response times for clients.

It also handles the Vary header more intelligently, creating separate cache entries for different content types. This prevents clients from getting the wrong version of a resource, which is a common headache with caching.