Course contentsShow
← Cloud and Infrastructure
Lesson 1222 of 2,98924. Kubernetes NetworkingFree lesson

Installing NGINX Ingress Controller

Deploy the NGINX Ingress Controller using Helm or manifests and verify it's ready to handle traffic.

Installing NGINX Ingress Controller

What you'll learn: How to deploy the NGINX Ingress Controller to enable HTTP/HTTPS routing into your Kubernetes cluster.

Why Install an Ingress Controller?

Remember that an Ingress resource is just a configuration blueprint (like a recipe). The Ingress Controller is the actual implementation (the chef who cooks). Without installing a controller, your Ingress resources do nothing. NGINX Ingress Controller is one of the most popular choices—it reads your Ingress rules and configures NGINX to route traffic accordingly.

Installation Methods

You have two primary approaches:

1. Using Manifests (Direct YAML) Apply the official manifests directly from the NGINX project:

kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.8.1/deploy/static/provider/cloud/deploy.yaml

This creates a namespace (ingress-nginx), a Deployment, a LoadBalancer Service, and necessary RBAC resources.

2. Using Helm (Recommended for Customization) Helm makes configuration easier and repeatable:

helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx
helm repo update
helm install nginx-ingress ingress-nginx/ingress-nginx

Verifying Installation

Check that the controller pods are running:

kubectl get pods -n ingress-nginx

Look for a pod with status Running. Verify the service has an external IP (if using LoadBalancer):

kubectl get service -n ingress-nginx

You should see an EXTERNAL-IP assigned (or <pending> initially on cloud providers). This IP becomes the entry point for all HTTP/HTTPS traffic routed by your Ingress resources.

Key Takeaway: Installing the NGINX Ingress Controller transforms your cluster to handle external web traffic—use manifests for quick starts or Helm for production flexibility, then verify pods are running and the LoadBalancer service has an external IP.