Phase 5 - AKS with Azure DNS + NGINX Ingress + cert-manager

In this lab, we built a production-grade HTTPS setup for applications running on: Azure Kubernetes Service Azure DNS NGINX Ingress Controller cert-manager Let's Encrypt We exposed: hello.az.innopy.dev api.az.innopy.dev And secured them with valid public TLS certificates. This guide includes: ✅ Azure DNS zone setup ✅ A record configuration ✅ cert-manager configuration ✅ TLS-enabled Ingress ✅ Complete troubleshooting section 🏗 Architecture Overview User (HTTPS) ↓ Azure Public IP ↓ Azure Load Balancer ↓ NGINX Ingress Controller ↓ Kubernetes Services ↓ Pods For certificate issuance: cert-manager ↓ Let's Encrypt (HTTP-01 challenge) ↓ Temporary solver ingress ↓ Validation ↓ TLS Secret stored in cluster 🌍 Step 1 — Create Azure DNS Zone If you don’t already have the zone: az network dns zone create \ --resource-group <dns-rg> \ --name az.innopy.dev Verify: az network dns zone list -o table 🌐 Step 2 — Point Subdomains to AKS Ingress Get your NGINX public IP: kubectl get svc -n ingress-nginx Set