Skip to content
SPECIFICTION
Get listed

HAProxy Ingress

haproxy-ingress.github.io

Free plan LinuxSelf-hosted
Visit haproxy-ingress.github.io
Spec score 7.6 #13 of 28 in Kubernetes Ingress Controllers

What it is

HAProxy Ingress is a free, self-hosted controller that configures HAProxy to route external requests to applications in a Kubernetes cluster. It applies changes made in the cluster to HAProxy without requiring a separate update process. The project supports Ingress and Gateway API resources and describes more than 200 configuration options. Gateway API support is partial: the documented implementation covers GatewayClass, Gateway, TCPRoute, and HTTPRoute, but not HTTPRoute filters or resource status updates. Installation uses a Helm chart and requires Helm 3, a running Kubernetes cluster, and administrative privileges in that cluster. Version 0.16 requires Kubernetes 1.21 or newer. Local cluster options named by the project include minikube, kind, k3s, k3d, and colima. It associates requests with ingress hosts using TLS SNI and the Host header. Metrics can be collected with Prometheus and Grafana using Prometheus Operator. The project uses the Apache-2.0 license and lists community channels including Slack, a users mailing list, and Stack Overflow.

Spec sheet

Purpose
HAProxy Ingress configures HAProxy to route incoming requests from an external network to applications in a Kubernetes cluster.Read 29 Sep 2026 · github.com
Deployment
The controller is installed and configured with a Helm chart, and the instructions require Helm version 3.Read 29 Sep 2026 · haproxy-ingress.github.io
Security
The getting-started guide says HAProxy Ingress uses TLS SNI and the Host header to associate requests with ingress hosts.Read 29 Sep 2026 · haproxy-ingress.github.io
Support
The project lists a Kubernetes Slack channel, a users mailing list, and Stack Overflow for community discussion and questions.Read 29 Sep 2026 · github.com
License
The GitHub repository lists the project under the Apache-2.0 license.Read 29 Sep 2026 · github.com
Cluster requirement
HAProxy Ingress requires a running Kubernetes cluster, and its v0.16 controller requires Kubernetes 1.21 or newer.Read 29 Sep 2026 · haproxy-ingress.github.io
Customization
The project homepage describes more than 200 configuration options and support for Ingress and Gateway API resources.Read 29 Sep 2026 · haproxy-ingress.github.io
Dynamic updates
Changes made to the Kubernetes cluster are applied to the HAProxy instance on the fly.Read 29 Sep 2026 · github.com
Gateway API
The Gateway API documentation says HAProxy Ingress can manage Ingress and Gateway API resources in the same cluster, with support described as partial.Read 29 Sep 2026 · haproxy-ingress.github.io
Gateway API limits
The documented Gateway API implementation supports GatewayClass, Gateway, TCPRoute, and HTTPRoute, while HTTPRoute filters and resource status updates are not implemented on that page’s described version.Read 29 Sep 2026 · haproxy-ingress.github.io
Installation privilege
The installation guide says administrative privileges in the Kubernetes cluster are required to install the controller properly.Read 29 Sep 2026 · haproxy-ingress.github.io
Monitoring integrations
The metrics example describes collecting HAProxy and controller metrics with Prometheus and Grafana using Prometheus Operator.Read 29 Sep 2026 · haproxy-ingress.github.io
Supported local clusters
The getting-started guide names minikube, kind, k3s, k3d, and colima as local Kubernetes deployment options.Read 29 Sep 2026 · haproxy-ingress.github.io

Plans and prices

HAProxy Ingress Free Kubernetes cluster required · v0.16 requires Kubernetes 1.21 or newer Read 29 Sep 2026 · haproxy-ingress.github.io

Every HAProxy Ingress plan and price →

Strong points and limits

Strong points

  • Free and self-hosted.
  • Applies cluster changes to HAProxy on the fly.
  • More than 200 configuration options are described.
  • Supports TLS automation, canary routing, and rate limiting.
  • Metrics can be collected with Prometheus and Grafana.

Limits

  • Requires a running Kubernetes cluster and Helm 3.
  • Installation requires administrative cluster privileges.
  • Gateway API support is partial.
  • Version 0.16 requires Kubernetes 1.21 or newer.

Who it suits

It suits Kubernetes operators who want a self-hosted HAProxy controller for routing to cluster applications. Teams considering Gateway API resources should account for the documented implementation gaps.

Verdict

HAProxy Ingress offers a no-cost controller with extensive configuration options and dynamic updates. Its Kubernetes and installation prerequisites, plus documented Gateway API omissions, are important constraints.

Where Specifiction places it

Alternatives to HAProxy IngressAll alternatives →