Skip to the content
Know your tech before you buy it. Makers: get listed from $49/mo

HAProxy Ingress

haproxy-ingress.github.io

  • Free plan
  • Linux
  • Self-hosted

What HAProxy Ingress is

HAProxy Ingress is a free, self-hosted controller that configures HAProxy to route external requests to applications in a Kubernetes cluster. Changes in the cluster are applied to HAProxy on the fly, and the project describes more than 200 configuration options. It supports Ingress and Gateway API resources, though the documented Gateway API implementation is partial: it supports 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 cluster privileges. Version 0.16 requires Kubernetes 1.21 or newer. The getting-started guide names minikube, kind, k3s, k3d, and colima as local cluster options. The controller associates requests with ingress hosts using TLS SNI and the Host header. Metrics can be collected with Prometheus and Grafana using Prometheus Operator. HAProxy Ingress is licensed under Apache-2.0; community discussion options include a Kubernetes Slack channel, a users mailing list, and Stack Overflow.

Who it suits

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

Good to know, and what to watch

  • Applies cluster changes to HAProxy on the fly
  • Supports Ingress and Gateway API resources
  • More than 200 configuration options described
  • Metrics can be collected with Prometheus and Grafana
  • Apache-2.0 licensed
  • Requires a running Kubernetes cluster
  • Installation requires Helm 3 and administrative privileges
  • Version 0.16 requires Kubernetes 1.21 or newer
  • Gateway API support lacks filters and status updates

HAProxy Ingress

Free

Free plan

The verdict

HAProxy Ingress provides self-hosted routing for Kubernetes with dynamic updates and extensive configuration options. Its cluster requirements and partial Gateway API implementation are key considerations.

What the maker publishes

Cluster requirement
HAProxy Ingress requires a running Kubernetes cluster, and its v0.16 controller requires Kubernetes 1.21 or newer. source
Customization
The project homepage describes more than 200 configuration options and support for Ingress and Gateway API resources. source
Deployment
The controller is installed and configured with a Helm chart, and the instructions require Helm version 3. source
Dynamic updates
Changes made to the Kubernetes cluster are applied to the HAProxy instance on the fly. source
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. source
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. source
Installation privilege
The installation guide says administrative privileges in the Kubernetes cluster are required to install the controller properly. source
License
The GitHub repository lists the project under the Apache-2.0 license. source
Monitoring integrations
The metrics example describes collecting HAProxy and controller metrics with Prometheus and Grafana using Prometheus Operator. source
Purpose
HAProxy Ingress configures HAProxy to route incoming requests from an external network to applications in a Kubernetes cluster. source
Security
The getting-started guide says HAProxy Ingress uses TLS SNI and the Host header to associate requests with ingress hosts. source
Support
The project lists a Kubernetes Slack channel, a users mailing list, and Stack Overflow for community discussion and questions. source
Supported local clusters
The getting-started guide names minikube, kind, k3s, k3d, and colima as local Kubernetes deployment options. source

Checked against the maker's pages on 29 Sept 2026.