Phase 3 - Deploying a Custom App to Azure Kubernetes Service Using Azure Container Registry

🚀 In this lab, we will: Create an Azure Container Registry (ACR) Build a custom Docker image in the cloud Deploy it to Azure Kubernetes Service (AKS) Expose it publicly using a LoadBalancer This is a production-style workflow used by modern cloud-native teams. 🏗 Architecture Overview Developer → ACR → AKS → Service (LoadBalancer) → Public IP We use: Azure Kubernetes Service (AKS) Azure Container Registry (ACR) Managed Identity for secure image pulls 🔧 Prerequisites You already created AKS: az aks create \ --resource-group aks-east2-rg \ --name aks-prod-east2 \ --location eastus2 \ --node-count 2 \ --network-plugin azure \ --enable-managed-identity \ --enable-oidc-issuer \ --enable-workload-identity \ --enable-addons monitoring Set variables: RG = aks-east2-rg CLUSTER = aks-prod-east2 ACR_NAME = akseast2acr $RANDOM LOCATION = eastus2 1️⃣ Register Required Azure Providers (Important) New subscriptions often need manual provider registration: az provider register --namespace Microsoft.Con