Getting Started

How to install HAProxy Ingress and expose the first service.

The following sections walk through steps to have HAProxy Ingress working, watching ingress resources and exposing services.


HAProxy Ingress needs a running Kubernetes cluster. Controller version v0.14 needs Kubernetes 1.19 or newer, see other supported versions in the README file. HAProxy Ingress also works fine on local k8s deployments like minikube, kind or k3d.

An ingress controller works exposing internal services to the external world, so another pre-requisite is that at least one cluster node is accessible externally. On cloud environments, a cloud load balancer can be configured to reach the ingress controller nodes.

HAProxy Ingress uses TLS SNI extension and the Host header to associate requests and ingress’ hosts. The easiest way to accomplish this on local environment is using A production environment should consider a dynamic DNS solution or a wildcard DNS record.


HAProxy Ingress uses Helm chart to install and configure the controller. See below some deployment instructions:

  1. Install helm, HAProxy Ingress requires version 3. See the installation instructions here.

  2. Add the HAProxy Ingress’ Helm repository. This will instruct Helm to find all available packages:

    $ helm repo add haproxy-ingress
  3. Check if kubeconfig points to the right cluster:

    $ kubectl cluster-info

    The default cluster can be changed either via kubectl config set-context <cluster-context> or adding --kube-context <cluster-context> in the helm command-line options.

    Note that the user needs administrative privileges in the cluster to properly install the controller.

  4. Create a haproxy-ingress-values.yaml file with custom parameters:

    Use the content below if HAProxy Ingress should expose HAProxy via a service loadbalancer, like ELB, kube-vip, ServiceLB (k3s), etc.

    # Expose HAProxy via a service loadbalancer
        enabled: true

    Use the content below to expose HAProxy via host port on all cluster nodes.

    # Expose HAProxy via host port on all cluster nodes
        enabled: true
      kind: DaemonSet
        useHostPort: true
        type: ClusterIP

    HAProxy Ingress chart documentation has all the available options. See also further documentation in the default values file.

  5. Install HAProxy Ingress using haproxy-ingress as the release name and haproxy-ingress-values.yaml file as the custom parameters:

    $ helm upgrade haproxy-ingress haproxy-ingress/haproxy-ingress\
      --create-namespace --namespace ingress-controller\
      --version 0.14.7\
      -f haproxy-ingress-values.yaml

    Note that the command upgrade above, along with the --install command-line option, starts a new HAProxy Ingress deployment if it is missing, or starts a rolling update if HAProxy Ingress is already installed. template can be used instead to generate the manifests without installing them - add either a redirect ... >haproxy-ingress-install.yaml to save the output, or --output-dir output/ command line option to save one file per manifest.

The controller should be running in a few seconds. There are four important customizations made in the example above:

  • --version: a good practice, this will ensure that you’ll have the same version installed even if a new release issued.
  • --namespace: we’re instructing helm to install HAProxy Ingress in the ingress-controller namespace. This namespace will be created if it does not exist yet. The default behavior, if namespace is not provided, is to deploy the controller in the kubectl’s current namespace.
  • ingressClassResource.enabled: This causes the helm chart to apply an IngressClass to your cluster. IngressClasses are how HAProxy Ingress knows which of your Ingresses it should control. IngressClasses replace the annotation used in Kubernetes versions before v1.18.
  • kind, daemonset.useHostPort and service.type, only used when service loadbalancer should not be used: disables service load balancer and exposes HAProxy via host port on all cluster nodes.

HAProxy Ingress’ Helm chart has a few more configuration options, see all of them in the chart documentation and in the default values file.

Deploy and expose

The following steps deploy an echoserver image and exposes it in the current namespace using an Ingress resource. See here how to expose using Gateway API.

  1. Create the echoserver’s deployment and service:

    $ kubectl --namespace default create deployment echoserver --image
    $ kubectl --namespace default expose deployment echoserver --port=8080
  2. Check if echoserver is up and running:

    $ kubectl -n default get pod -w
    NAME                          READY   STATUS    RESTARTS   AGE
    echoserver-5b6fb6dd96-68jwp   1/1     Running   0          27s
  3. Make HAProxy Ingress expose the echoserver service. Change echoserver.local value in the --rule option below to a hostname that resolves to an ingress controller node.

    Obs.: is a convenient service which converts a valid domain name to any IP, either public or local. See here how it works.

    $ kubectl --namespace default create ingress echoserver \
      --class=haproxy \
  4. Send a request to our echoserver.

    $ curl -k https://echoserver.local
    $ wget -qO- --no-check-certificate https://echoserver.local

What’s next

See what differs to expose services using Gateway API:

Learn more about Ingress and IngressClass resources:

HAProxy Ingress has lots of configuration options. See the following tips to get started faster:

Last modified June 16, 2024: update to v0.14.7 (aa2c1bd0)