Skip to content

Installation Guide


Generic Deployment

The following resources are required for a generic deployment.

Mandatory command

kubectl apply -f

Provider Specific Steps

There are cloud provider specific yaml files.

Docker for Mac

Kubernetes is available for Docker for Mac's Edge channel. Switch to the Edge channel and enable Kubernetes.

Create a service

kubectl apply -f


For standard usage:

minikube addons enable ingress

For development:

  1. Disable the ingress addon:
$ minikube addons disable ingress
  1. Execute make dev-env
  2. Confirm the nginx-ingress-controller deployment exists:
$ kubectl get pods -n ingress-nginx 
NAME                                       READY     STATUS    RESTARTS   AGE
default-http-backend-66b447d9cf-rrlf9      1/1       Running   0          12s
nginx-ingress-controller-fdcdcd6dd-vvpgs   1/1       Running   0          11s


In AWS we use an Elastic Load Balancer (ELB) to expose the NGINX Ingress controller behind a Service of Type=LoadBalancer. Since Kubernetes v1.9.0 it is possible to use a classic load balancer (ELB) or network load balancer (NLB) Please check the elastic load balancing AWS details page

Elastic Load Balancer - ELB

This setup requires to choose in which layer (L4 or L7) we want to configure the ELB:

  • Layer 4: use TCP as the listener protocol for ports 80 and 443.
  • Layer 7: use HTTP as the listener protocol for port 80 and terminate TLS in the ELB

For L4:

kubectl apply -f
kubectl apply -f

For L7:

Change line of the file provider/aws/service-l7.yaml replacing the dummy id with a valid one "arn:aws:acm:us-west-2:XXXXXXXX:certificate/XXXXXX-XXXXXXX-XXXXXXX-XXXXXXXX" Then execute:

kubectl apply -f
kubectl apply -f

This example creates an ELB with just two listeners, one in port 80 and another in port 443


Network Load Balancer (NLB)

This type of load balancer is supported since v1.10.0 as an ALPHA feature.

kubectl apply -f


kubectl apply -f

Important Note: proxy protocol is not supported in GCE/GKE


kubectl apply -f


Using NodePort:

kubectl apply -f

Verify installation

To check if the ingress controller pods have started, run the following command:

kubectl get pods --all-namespaces -l app=ingress-nginx --watch

Once the operator pods are running, you can cancel the above command by typing Ctrl+C. Now, you are ready to create your first ingress.

Detect installed version

To detect which version of the ingress controller is running, exec into the pod and run nginx-ingress-controller version command.

POD_NAME=$(kubectl get pods -n $POD_NAMESPACE -l app=ingress-nginx -o jsonpath={.items[0]})
kubectl exec -it $POD_NAME -n $POD_NAMESPACE -- /nginx-ingress-controller --version

Using Helm

NGINX Ingress controller can be installed via Helm using the chart stable/nginx-ingress from the official charts repository. To install the chart with the release name my-nginx:

helm install stable/nginx-ingress --name my-nginx

If the kubernetes cluster has RBAC enabled, then run:

helm install stable/nginx-ingress --name my-nginx --set rbac.create=true

Detect installed version:

POD_NAME=$(kubectl get pods -l app=nginx-ingress -o jsonpath={.items[0]})
kubectl exec -it $POD_NAME -- /nginx-ingress-controller --version