A 6-Session Deep Dive into the modern evolution of Kubernetes Routing & Azure Application Gateway for Containers (AGC)
Execute these directly in Azure Cloud Shell. Always run 'Down' when finished to nuke the resources and stop billing.
curl -sSL "https://raw.githubusercontent.com/imranshs08/job/main/16-Automation-Scripts/azure_agc_lab_manager.sh" | bash -s -- up
curl -sSL "https://raw.githubusercontent.com/imranshs08/job/main/16-Automation-Scripts/azure_agc_lab_manager.sh" | bash -s -- down
Understanding why Ingress is being replaced. Setup the new Azure AGC resources on AKS. Contains the SRE-grade YAML comparisons between legacy Ingress and modern Gateway.
✅ COMPLETED (1h 31m)Wiring up Azure DNS, Cert-Manager, and dynamically securing Gateway API endpoints with Let's Encrypt using wildcard certificates.
HTTPRoutes, header matching, rewrite/redirect rules, and advanced deployments (Canary/A-B traffic splitting).
Applying rigorous WAF policies, integrating Prometheus/Grafana, and exploring alternative controllers like NGINX and Traefik Gateways.
Standing up Envoy Gateway natively and comparing the new API with traditional NGINX Ingress objects.
End-to-end production CI/CD architectures mapping Infrastructure to App using Terraform, ArgoCD, and Multi-Domain TLS architecture.
| Kubernetes Object | Responsibility / Pattern |
|---|---|
GatewayClass |
Template defining infrastructure implementation (e.g., Azure AGC, Envoy). Cluster scope. |
Gateway |
Physical/logical load balancer containing Listeners (Port 80/443, TLS details). Typically managed by Infra namespace. |
HTTPRoute |
Defines traffic routing (hostname, paths, headers) to backend Services. App Dev namespace. |
ReferenceGrant |
Strict security boundary allowing Cross-Namespace attachments (e.g., App Route attaching to Infra Gateway). |
| Vendor Annotations | Eliminated from Developer routes. Required ONLY on the Gateway object natively.
|