Phase 4 - Exposing Multiple Services on AKS Using NGINX Ingress

In this lab, we moved beyond a simple LoadBalancer and implemented Layer 7 routing using NGINX Ingress on: Azure Kubernetes Service (AKS) NGINX Ingress Controller By the end, we achieved: http://<PUBLIC-IP>/hello http://<PUBLIC-IP>/api Using: One public IP One Ingress controller Multiple backend services 🏗 Why Use Ingress Instead of LoadBalancer? With a normal Service: type: LoadBalancer You get: 1 Service = 1 Public IP That becomes expensive and hard to manage. With Ingress: 1 Public IP → Multiple routes → Multiple services This is how real microservices platforms operate. 🧱 Architecture Internet ↓ Azure LoadBalancer (created by ingress) ↓ NGINX Ingress Controller ↓ hello-service api-service The LoadBalancer is automatically created when installing the Ingress controller. 1️⃣ Install NGINX Ingress Controller We deployed the official controller: kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/main/deploy/static/provider/cloud/deploy.yaml Check readiness: kub