HAProxy Ingress connects Kubernetes routing rules to HAProxy, the proxy that receives requests and forwards them to application services. It is useful for publishing services through a common entry point while keeping routes in Kubernetes configuration. This community project's repository now resolves to N42 Gateway. It remains distinct from HAProxy Technologies' separate controller, so a matching proxy name does not mean their annotations, charts or upgrade procedures are interchangeable.
Deployment and operating notes
The recovered jcmoraisjr/haproxy-ingress repository now redirects to N42 Gateway. Its current README describes an Ingress and Gateway API controller, while the older HAProxy Ingress documentation still describes release-specific deployment settings. Check the selected release’s naming, chart and API support rather than applying the main branch’s instructions to an older controller. Its controller class and configuration keys differ from haproxytech/kubernetes-ingress. The shared HAProxy data plane does not make their annotations or chart values interchangeable, and community ingress-nginx retirement does not retire either HAProxy implementation.
Identify the running image, controller class and chart before planning an upgrade. Inventory annotations, ConfigMaps, TLS settings, rewrites, authentication and TCP services. Use the release-specific Kubernetes compatibility guidance and chart from the matching project. If migrating between controllers or toward Gateway API, test routing and policy behavior on a separate address, including denied requests, path boundaries and certificate selection. Ensure each controller watches only its intended resources during the overlap. Preserve original objects and a traffic rollback path until the replacement is proven. Do not copy a configuration example from the other HAProxy controller merely because the option has a similar name.
Historical upstream link check · 2026-10-09
The recorded upstream address redirects to https://github.com/n42-gateway/n42-gateway/blob/master/README.md and returned HTTP 200 on 2026-10-09. GitHub does not mark n42-gateway/n42-gateway archived or disabled; this does not establish active maintenance, support or compatibility. GitHub resolves the old repository identity to n42-gateway/n42-gateway. Link availability does not certify the historical installation instructions or current security support.
Website availability is separate from project, chart and image support. Use the current guidance and primary sources on this page to assess the distribution.
Historical Kubedex content
Preserved for context. Commands, versions, prices and results below reflect the original research.
haproxy-ingress is an Ingress controller that uses ConfigMap to store the haproxy configuration. This chart bootstraps an haproxy-ingress deployment on a Kubernetes cluster using the Helm package manager.
You may be interested in our ingress comparison article.
What is an Ingress?
Typically, services and pods have IPs only routable by the cluster network. All traffic that ends up at an edge router is either dropped or forwarded elsewhere.
An Ingress is a collection of rules that allow inbound connections to reach the cluster services.
It can be configured to give services externally-reachable URLs, load balance traffic, terminate SSL, offer name-based virtual hosting, and more. Users request ingress by POSTing the Ingress resource to the API server. An Ingress controller is responsible for fulfilling the Ingress, usually with a load balancer, though it may also configure your edge router or additional frontends to help handle the traffic in an HA manner.
What is HaProxy?
HAProxy is a free, very fast and reliable solution offering high availability, load balancing, and proxying for TCP and HTTP-based applications. It is particularly suited for very high traffic websites and powers quite a number of the world’s most visited ones. Over the years it has become the de-facto standard opensource load balancer, is now shipped with most mainstream Linux distributions, and is often deployed by default in cloud platforms.
HAProxy Ingress images are built by Travis CI and the image is deployed from Travis CI to Quay.io whenever a tag is applied. The latest tag will always point to the latest stable version while canary tag will always point to the latest beta-quality and release-candidate versions.
Before the beta-quality releases, the source code could also be tagged and images deployed. The snapshot tag will always point to the latest tagged version, which could be a release, a beta-quality or a development version.
Configuration
HAProxy Ingress has two types of dynamic configurations: per ingress resource using annotations, or globally using a ConfigMap resource. The controller has also static command-line arguments.
It is also possible to change the default template mounting a new template file at /etc/haproxy/template/haproxy.tmpl. This is the only file in the directory, so create a configmap with haproxy.tmpl key mounting into /etc/haproxy/template will work.
Sources & further reading
Spotted something that needs another look?
Help improve this page →