Deploying HAProxy in Kubernetes

The HAProxy Kubernetes ingress controller provides a way to route traffic into your Kubernetes cluster while providing load balancing and other features.

For more information, refer to your Kubernetes documentation.

Before You Begin

Ensure that you have downloaded and configured the prerequisite software. For more information, see Downloading kubectl and Helm.

Guideline for Configuring HAProxy in Azure

ScanCentral DAST integration with Kubernetes does not require an external or public IP address. Use caution with your ingress controller configuration to ensure that you do not expose the ingress controller into the Internet. This exposure will not happen in local Kubernetes clusters. However, an Azure ingress controller could be exposed to the Internet using a public IP address.

To prevent using a public IP address in Azure, use the following command for HAProxy Helm install:

For details about using an ingress controller with restricted public access in Azure, refer to Microsoft documentation.

Deploying HAProxy Ingress Controller

To deploy the HAProxy ingress controller:

• On the machine where the kubectl client and Helm are installed, enter the following in PowerShell:

  kubectl label node <node-name> role=ingress-controller
  helm repo add haproxy-ingress https://haproxy-ingress.github.io/charts
  helm install haproxy-ingress haproxy-ingress/haproxy-ingress `
      --create-namespace --namespace=ingress-controller `
      --set controller.hostNetwork=true `
      --set controller.nodeSelector.role=ingress-controller `
      --set controller.service.type=LoadBalancer `
      --set-string controller.service.annotations.'service\.beta\.
        kubernetes\.io/azure-load-balancer-internal'=true 

To confirm that the HAProxy ingress has started:

• Enter the following in PowerShell:

  kubectl --namespace ingress-controller get services haproxy-ingress -o wide
  

  You should see a response similar to the following:

  NAME              TYPE           CLUSTER-IP       EXTERNAL-IP
        PORT(S)                      AGE
  haproxy-ingress   LoadBalancer   <ip_address>  <Pending>
       80:31255/TCP,443:30766/TCP   34s