Install on Google GKE

This section shows you how to install the HAProxy Enterprise Kubernetes Ingress Controller in Google Kubernetes Engine.

Pre-installation checklist Jump to heading #

• A running GKE Kubernetes cluster
• The Google Cloud SDK
• The helm command-line tool
• The kubectl command-line tool

Connect to your GKE cluster Jump to heading #

1. Connect to your cluster using the gcloud command-line tool:

   nix
   gcloud init
   gcloud container clusters get-credentials [Your cluster name] --zone [Your zone] --project [Your project name]

   nix
   gcloud init
   gcloud container clusters get-credentials [Your cluster name] --zone [Your zone] --project [Your project name]

2. Check that you can access the cluster by calling kubectl get pods:

   nix
   kubectl get pods

   nix
   kubectl get pods

   If your cluster is new it may not have any resources:

   output
   text
   No resources found in default namespace.

   output
   text
   No resources found in default namespace.

Install Jump to heading #

Choose one of the following installation methods:

Install with Helm Jump to heading #

1. Add the HAProxy Technologies Helm repository:

   nix
   helm repo add haproxytech https://haproxytech.github.io/helm-charts

   nix
   helm repo add haproxytech https://haproxytech.github.io/helm-charts

2. Update your list of charts:

   nix
   helm repo update

   nix
   helm repo update

3. Install the ingress controller, replacing [KEY] with your HAProxy Enterprise license key:

   nix
   helm 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

   nix
   helm 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

   This will create a Google Cloud 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 use Ingress resources only if they specify an annotation of kubernetes.io/ingress.class: haproxy. You can disable this by setting --set controller.ingressClass=null when calling helm install.

Install with kubectl Jump to heading #

1. Download the deployment YAML file (v1.11).

   Other versions

   • Deployment YAML File (v1.9)

   • Deployment YAML File (v1.8)

   • Deployment YAML File (v1.7)

   • Deployment YAML File (v1.6)

   • Deployment YAML File (v1.5)

   • Deployment YAML File (v1.4)

2. Edit the haproxy-ingress Service object in the YAML file, setting its type field to LoadBalancer:

   haproxy-ingress.hapee.yaml
   yaml
   apiVersion: v1
   kind: Service
   metadata:
     labels:
       run: haproxy-ingress
     name: haproxy-ingress
     namespace: haproxy-controller
   spec:
     selector:
       run: haproxy-ingress
     type: LoadBalancer

   haproxy-ingress.hapee.yaml
   yaml
   apiVersion: v1
   kind: Service
   metadata:
     labels:
       run: haproxy-ingress
     name: haproxy-ingress
     namespace: haproxy-controller
   spec:
     selector:
       run: haproxy-ingress
     type: LoadBalancer

3. Use the kubectl apply command to deploy the controller:

   nix
   kubectl apply -f haproxy-ingress.hapee.yaml

   nix
   kubectl apply -f haproxy-ingress.hapee.yaml

   This will create a Google Cloud 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.

4. Use kubectl create secret to store your credentials for the private HAProxy Docker registry, replacing KEY with your HAProxy Enterprise license key:

   nix
   kubectl create secret docker-registry regcred --namespace=haproxy-controller --docker-server=kubernetes-registry.haproxy.com --docker-username=<KEY> --docker-password=<KEY>

   nix
   kubectl create secret docker-registry regcred --namespace=haproxy-controller --docker-server=kubernetes-registry.haproxy.com --docker-username=<KEY> --docker-password=<KEY>

   output
   text
   secret/regcred created

   output
   text
   secret/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

output
text
NAME                                        READY   STATUS    RESTARTS   AGE
haproxy-kubernetes-ingress-7dd4cc4b-x5fkv   1/1     Running   0          1m

output
text
NAME                                        READY   STATUS    RESTARTS   AGE
haproxy-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

output
text
NAME                         TYPE           CLUSTER-IP   EXTERNAL-IP   PORT(S)                                     AGE
haproxy-kubernetes-ingress   LoadBalancer   10.8.14.69   34.68.15.92   80:32693/TCP,443:30866/TCP,1024:32181/TCP   45s

output
text
NAME                         TYPE           CLUSTER-IP   EXTERNAL-IP   PORT(S)                                     AGE
haproxy-kubernetes-ingress   LoadBalancer   10.8.14.69   34.68.15.92   80:32693/TCP,443:30866/TCP,1024:32181/TCP   45s