Azure Kubernetes Service AGIC Ingress: 30 Real-World Demos

Learn how the Azure AGC ingress controller uses a greenfield add-on on AKS to connect Kubernetes services to the Azure Application Gateway, enabling layer 7 routing and seamless gateway config.

Create an AKS cluster in East US with the AGIC addon and an application gateway using Azure CLI, enable the network plugin and managed identity, then verify in the portal.

Assigns the network contributor role to the AGIC addon managed identity to grant subnet access, and shows how to locate the application gateway subnet ID and add on identity ID.

Verify the AKS cluster and ingress app gateway using kubectl and Azure portal, confirm the ingress app gateway deployment and version 1.5.3, understand add-on versus helm differences.

Learn cost saving by stopping the application gateway and AKS cluster when not in use, using a single gateway, manual scaling, and CLI stop commands with optional deletion.

Learn how to implement an ingress default backend in Azure Kubernetes Service with AGIC, wiring a deployment to a cluster IP service and Application Gateway backend pool.

Deploy and verify an ingress with default backend in Azure Kubernetes Service by applying the manifest, creating deployment, cluster IP service, and ingress service; inspect via kubectl and application gateway.

Review the application gateway in detail, verify backend pools and health probes, then test and clean up, preparing for subsequent ingress with http rules.

Introduce http rules and paths for Azure application gateway ingress, deploy app one with a cluster ip service and ingress, and validate routes for slash app one and related paths.

Review ingress manifests in Kubernetes, focusing on ingress class name, rules, and path types (prefix and exact) with backends and services, and verify nginx app deployment and cluster IP service.

Deploy AGIC ingress paths, create app1 Nginx deployment, service, and ingress, and verify routing for root and /app1 with a health probe on Azure Application Gateway.

Scale a Kubernetes deployment from one to five replicas, then verify the new pods and their IPs. The ingress controller automatically propagates these changes to the application gateway backend pool.

Deploy three apps on AKS and configure an ingress service with path rules for /app1, /app2, and root; ingress controller translates these to Application Gateway routing with backends and probes.

Demonstrate AKS url routing using AGIC ingress with a default backend and path-based routes for three apps, and verify with the Azure Application Gateway backend pools and probes.

Demonstrates url routing with http path root context in an ingress by deploying the zero two cube manifest and testing app1, app2, and root context via kubectl.

Learn to use the backend path prefix annotation in ingress to rewrite internet URLs to the app's internal context root across path based routing.

Showcases implementing the backend path prefix annotation for the Azure application gateway ingress controller, deploying Kubernetes manifests, and validating path-based routing from the internet to the app.

Learn how to implement back end hostname annotation in an ingress service using an echo server to show how hostname overrides affect requests from the internet to internal applications.

Demonstrates implementing the backend hostname annotation for an echo server ingress behind Azure Application Gateway, enabling and observing host header overrides to a specific domain and comparing outputs.

Learn cookie based affinity annotations in Azure Kubernetes Service ingress for the echo server, persisting sessions to specific pods via application gateway cookies and enabling distinct names for multi-app setups.

Enable cookie based affinity in the AGIC ingress and deploy three eco server pods to verify persistent routing to a single pod, using browser devtools and application gateway settings.

Enable cookie based affinity and distinct cookie names per backend in an Azure Kubernetes Service AGIC ingress, then verify the distinct cookie with browser dev tools and kubectl commands.

Override frontend port annotation demonstration shows deploying an app, applying the ingress override frontend port to change app gateway listener from 80 to 8080, and validating access via 8080.

Create a rewrite rule set in the azure application gateway and reference it in ingress annotations to pass a custom header to the back end, verified with an echo server.

Deploy and verify a rewrite rule set annotation in Azure Application Gateway, create a custom my domain header, and apply it to the ingress for the echo server.