HAProxy Ingress review
A broad, self-hosted ingress option with Ingress and Gateway API support.
Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026
HAProxy Ingress is an open-source Kubernetes ingress controller for routing external HTTP, HTTPS, and TCP traffic to applications running in a cluster. It fits teams that want broad traffic-management capabilities while keeping deployment self-hosted. The controller supports Kubernetes Ingress resources and Gateway API resources, including Gateway, HTTPRoute, TLSRoute, TCPRoute, and ReferenceGrant. Its HAProxy foundation also gives it a clear fit for environments already using HAProxy for application traffic.
Feature coverage is the main reason to consider it. ACME-based certificate issuance and renewal handle TLS automation, while client-IP rate limiting and concurrent connection limits support traffic control. Blue/green weighted routing can select traffic by header or cookie, which suits controlled releases and canary-style delivery. External authentication and OAuth2 Proxy integration address authentication flows, and ModSecurity or Coraza integration adds web application firewall options. The combination is broader than a controller focused only on basic HTTP routing.
The platform and ecosystem fit are centered on Kubernetes, HAProxy, and Gateway API, with additional integration points for ModSecurity, Coraza, and OAuth2 Proxy. It supports Linux and self-hosted deployment, so teams should be prepared to operate the controller within their own Kubernetes environment. HAProxy Ingress is a strong choice for organizations that need routing across HTTP, HTTPS, and TCP alongside security and traffic-policy features. Teams seeking a narrowly focused ingress layer or a managed hosting model should look elsewhere.
HAProxy Ingress pros and cons
- Where it wins
- Supports both Kubernetes Ingress resources and Gateway API
- Automates ACME certificate issuance and renewal
- Adds canary routing, rate limits, authentication, and WAF integrations
- Where it doesn't
- Self-hosted deployment requires Kubernetes and Linux infrastructure
- HAProxy-based configuration may be more than simple ingress needs
- Commercial pricing and managed hosting are not part of the offering
HAProxy Ingress fact sheet, pricing and score →
Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.
Last updated · How we research and update