Official HAProxy Technologies Helm charts for running HAProxy on Kubernetes: as a plain load balancer, as an Ingress controller, or as a Gateway API controller.
| Chart | Deploys | Kubernetes | Latest |
|---|---|---|---|
kubernetes-ingress |
HAProxy Kubernetes Ingress Controller: Ingress, IngressClass and Gateway API support | 1.23+ | |
haproxy-unified-gateway |
HAProxy Unified Gateway: a Kubernetes Gateway API controller | 1.26+ | |
haproxy |
HAProxy as a workload, configured from values.yaml; no controller |
1.17+ |
Each chart's README.md lists its configuration options and installation examples.
- A Kubernetes cluster at the version the chart needs (see the table). For a local one, kind or minikube will do; otherwise see Getting started.
- Helm 3.8 or newer (needed for OCI registries).
Charts are published to a Helm repository and, as OCI artifacts, to the GitHub Container Registry. Use either.
helm repo add haproxytech https://haproxytech.github.io/helm-charts
helm repo update
helm search repo haproxytech/
helm install my-release haproxytech/<chart>helm install my-release oci://ghcr.io/haproxytech/helm-charts/<chart>Pin a release with --version <version>. The charts are also listed on Artifact Hub.
Chart changes are listed on Artifact Hub: kubernetes-ingress, haproxy-unified-gateway, haproxy.
Release notes for the software the charts deploy: HAProxy Kubernetes Ingress Controller, HAProxy Unified Gateway, HAProxy.
Contributions are welcome; see CONTRIBUTING.md. In short: sign off every commit (git commit -s), bump the chart version in Chart.yaml for any chart change, and send changes to different charts as separate pull requests. test/README.md explains how to lint and test charts locally, with or without a cluster.
