Installation
Install on Azure AKS
This section shows you how to install HAProxy Enterprise Kubernetes Ingress Controller in Azure Kubernetes Service.
Pre-installation checklist Jump to heading
- A running AKS Kubernetes cluster
- The Azure CLI
- The helm command-line tool
- The kubectl command-line tool
Connect to your AKS cluster Jump to heading
-
Connect to your cluster using the Azure CLI:
nixaz account set --subscription [Your Azure subscription ID]az aks get-credentials --resource-group [Your resource group] --name [Your AKS cluster name]nixaz account set --subscription [Your Azure subscription ID]az aks get-credentials --resource-group [Your resource group] --name [Your AKS cluster name] -
Check that you can access the cluster by calling
kubectl get pods
:nixkubectl get podsnixkubectl get podsIf your cluster is new it may not have any resources:
outputtextNo resources found in default namespace.outputtextNo resources found in default namespace.
Install Jump to heading
Choose one of the following installation methods:
Install with Helm Jump to heading
Helm values file
The following example uses --set
invocations to configure the ingress controller. When installing with Helm, you can instead use a Helm values file to provide your configuration values. Using a Helm values file can provide for better traceability of configuration changes and reduce the complexity of Helm installation commands.
-
Add the HAProxy Technologies Helm repository:
nixhelm repo add haproxytech https://haproxytech.github.io/helm-chartsnixhelm repo add haproxytech https://haproxytech.github.io/helm-charts -
Update your list of charts:
nixhelm repo updatenixhelm repo update -
Install the ingress controller, replacing
[KEY]
with your HAProxy Enterprise license key:nixhelm install haproxy-kubernetes-ingress haproxytech/kubernetes-ingress \--create-namespace \--namespace haproxy-controller \--set controller.imageCredentials.registry=kubernetes-registry.haproxy.com \--set controller.imageCredentials.username=[KEY] \--set controller.imageCredentials.password=[KEY] \--set controller.image.repository=kubernetes-registry.haproxy.com/hapee-ingress \--set controller.image.tag=v1.11 \--set controller.service.type=LoadBalancer \--set controller.service.annotations."service\.beta\.kubernetes\.io/azure-load-balancer-health-probe-request-path"="/healthz"nixhelm install haproxy-kubernetes-ingress haproxytech/kubernetes-ingress \--create-namespace \--namespace haproxy-controller \--set controller.imageCredentials.registry=kubernetes-registry.haproxy.com \--set controller.imageCredentials.username=[KEY] \--set controller.imageCredentials.password=[KEY] \--set controller.image.repository=kubernetes-registry.haproxy.com/hapee-ingress \--set controller.image.tag=v1.11 \--set controller.service.type=LoadBalancer \--set controller.service.annotations."service\.beta\.kubernetes\.io/azure-load-balancer-health-probe-request-path"="/healthz"This will create an Azure Load Balancer that routes traffic to the ingress controller service. You can map the load balancer’s IP address to your public DNS domain name.
By default, the Helm chart adds
--ingress.class=haproxy
to the ingress controller. That means that it will useIngress
resources only if they specify an annotation ofkubernetes.io/ingress.class: haproxy
. You can disable this by setting--set controller.ingressClass=null
when callinghelm install
.
Install with kubectl Jump to heading
-
Download the deployment YAML file (v1.11).
-
Edit the
haproxy-ingress
Service object in the YAML file, setting itstype
field toLoadBalancer
:haproxy-ingress.hapee.yamlyamlapiVersion: v1kind: Servicemetadata:labels:run: haproxy-ingressname: haproxy-ingressnamespace: haproxy-controllerspec:selector:run: haproxy-ingresstype: LoadBalancerhaproxy-ingress.hapee.yamlyamlapiVersion: v1kind: Servicemetadata:labels:run: haproxy-ingressname: haproxy-ingressnamespace: haproxy-controllerspec:selector:run: haproxy-ingresstype: LoadBalancer -
Use the
kubectl apply
command to deploy the controller:nixkubectl apply -f haproxy-ingress.hapee.yamlnixkubectl apply -f haproxy-ingress.hapee.yamlThis will create an Azure Load Balancer that routes traffic to the ingress controller service. You can map the load balancer’s IP address to your public DNS domain name.
-
Use
kubectl create secret
to store your credentials for the private HAProxy Docker registry, replacing KEY with your HAProxy Enterprise license key:nixkubectl create secret docker-registry regcred --namespace=haproxy-controller --docker-server=kubernetes-registry.haproxy.com --docker-username=<KEY> --docker-password=<KEY>nixkubectl create secret docker-registry regcred --namespace=haproxy-controller --docker-server=kubernetes-registry.haproxy.com --docker-username=<KEY> --docker-password=<KEY>outputtextsecret/regcred createdoutputtextsecret/regcred created
Check your installation Jump to heading
Verify that the controller is installed into your Kubernetes cluster by using the command kubectl get pods
:
nix
kubectl get pods --namespace haproxy-controller
nix
kubectl get pods --namespace haproxy-controller
outputtext
NAME READY STATUS RESTARTS AGEhaproxy-kubernetes-ingress-7dd4cc4b-x5fkv 1/1 Running 0 1m
outputtext
NAME READY STATUS RESTARTS AGEhaproxy-kubernetes-ingress-7dd4cc4b-x5fkv 1/1 Running 0 1m
Get the External IP, which you can use to access your cluster:
nix
kubectl get services --namespace haproxy-controller
nix
kubectl get services --namespace haproxy-controller
outputtext
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGEhaproxy-kubernetes-ingress LoadBalancer 10.0.40.8 20.62.154.138 80:31669/TCP,443:30449/TCP,1024:31713/TCP 2m43s
outputtext
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGEhaproxy-kubernetes-ingress LoadBalancer 10.0.40.8 20.62.154.138 80:31669/TCP,443:30449/TCP,1024:31713/TCP 2m43s
Do you have any suggestions on how we can improve the content of this page?