Phase 2: Deploying a Production-Ready AKS Cluster in East US 2 (Azure CNI + Managed Identity + Monitoring)

In Phase 1, we prepared: Resource Group Virtual Network + Subnet Managed Identity Provider registrations Now we deploy a production-grade AKS cluster in eastus2 using best practices. This is not a demo cluster. This is how platform engineers deploy AKS in real environments. 🎯 Architecture Goal We will create: AKS attached to existing VNet Azure CNI networking (not kubenet) Managed Identity (no service principal) OIDC issuer enabled Workload Identity enabled Azure Monitor integration enabled Separate system/user node pools (optional) Integrated services: Kubernetes Azure Virtual Network Azure Monitor Log Analytics 🛠 Step 1 — Get Required Resource IDs AKS must be attached to an existing subnet. Get Subnet ID SUBNET_ID = $( az network vnet subnet show \ --resource-group aks-east2-rg \ --vnet-name aks-vnet \ --name aks-subnet \ --query id -o tsv ) Get Managed Identity ID MI_ID = $( az identity show \ --resource-group aks-east2-rg \ --name aks-mi \ --query id -o tsv ) MI_PRINCIPAL_ID = $( a