Skip to content

External_ApplicationGateway_Ingress_Controller.md

Latest commit

 

History

History
163 lines (116 loc) · 4.34 KB

External_ApplicationGateway_Ingress_Controller.md

File metadata and controls

163 lines (116 loc) · 4.34 KB

External Application Gateway Ingress Controller

Exercise Overview: External Application Gateway Ingress Controller Setup. This exercise guides participants through the process of setting up an Azure Kubernetes Service (AKS) cluster with an Application Gateway Ingress Controller, facilitating external access to applications.

Requirements

  • Azure Kubernetes Service (AKS) Cluster (Perform steps 1 to 4 if not already running)
  • Application Gateway V2 + Public IP
Solution

1. Create Resource Group

Creates an Azure Resource Group for organizing and managing resources.

az group create --location westeurope --resource-group demo-weu-rg

2. Create SSH RSA Keys

Generates SSH RSA keys for secure communication.

ssh-keygen -t rsa

3. Create Azure Kubernetes Service

Deploys an AKS cluster with specified configurations.

az aks create \
  --location westeurope \
  --subscription <Your-Subscription-ID> \
  --resource-group demo-weu-rg \
  --name <Your-AKS-Cluster-Name> \
  --ssh-key-value $HOME/.ssh/id_rsa.pub \
  --network-plugin kubenet \
  --load-balancer-sku standard \
  --outbound-type loadBalancer \
  --node-vm-size Standard_B2s \
  --node-count 1 \
  --tags 'ENV=Demo' 'OWNER=Corporation Inc.'

4. Get Kubeconfig

Retrieves and merges the AKS cluster's kubeconfig into the local environment.

az aks get-credentials \
  --resource-group demo-weu-rg \
  --name <Your-AKS-Cluster-Name> \
  --admin

5. Create Empty Application Gateway + VNET + SUBNET + IP

Creates an Application Gateway with a dedicated VNET, subnet, and public IP address.

az network vnet create \
  --name myVNet \
  --resource-group demo-weu-rg \
  --location westeurope \
  --address-prefix 10.21.0.0/16 \
  --subnet-name myAGSubnet \
  --subnet-prefix 10.21.0.0/24

az network vnet subnet create \
  --name myBackendSubnet \
  --resource-group demo-weu-rg \
  --vnet-name myVNet   \
  --address-prefix 10.21.1.0/24

az network public-ip create \
  --resource-group demo-weu-rg \
  --name myAGPublicIPAddress \
  --allocation-method Static \
  --sku Standard

az network application-gateway create --resource-group demo-weu-rg --name AGW1 --vnet-name MyVNet --subnet myAGSubnet --public-ip-address myAGPublicIPAddress --sku Standard_v2 --capacity 1 --frontend-port 80 --http-settings-port 80 --priority 1000

6. Connect Application Gateway to AKS

Enables the Ingress Application Gateway add-on for AKS and associates it with the created Application Gateway.

az aks enable-addons -n <Your-AKS-Cluster-Name> -g demo-weu-rg -a ingress-appgw --appgw-id "/subscriptions/<Your-Subscription-ID>/resourceGroups/demo-weu-rg/providers/Microsoft.Network/applicationGateways/AGW1"

7. VNet Peering (App Gateway VNet <-> AKS VNet)

Establishes VNet peering between the Application Gateway VNet and the AKS-managed VNet, allowing traffic flow.

First, get the AKS VNet ID:

AKS_VNET_ID=$(az network vnet list --query "[?contains(name, 'aks-vnet') && contains(resourceGroup, 'MC_demo-weu-rg')].[id]" -o tsv)

Then, get your App Gateway VNet name:

APPGW_VNET_ID=$(az network vnet show -n myVNet -g demo-weu-rg --query id -o tsv)

Now create peering from AppGW to AKS:

az network vnet peering create \
  --name AppGWToAKS \
  --resource-group demo-weu-rg \
  --vnet-name myVNet \
  --remote-vnet "$AKS_VNET_ID" \
  --allow-vnet-access

And peering from AKS to AppGW (use the autogenerated resource group):

AKS_RG=$(az aks show -g demo-weu-rg -n <Your-AKS-Cluster-Name> --query nodeResourceGroup -o tsv)

az network vnet peering create \
  --name AKSToAppGW \
  --resource-group "$AKS_RG" \
  --vnet-name $(basename "$AKS_VNET_ID") \
  --remote-vnet "$APPGW_VNET_ID" \
  --allow-vnet-access

8. Deploy Example Application

Deploys a sample application on the AKS cluster.

kubectl apply -f https://raw.githubusercontent.com/Azure/application-gateway-kubernetes-ingress/master/docs/examples/aspnetapp.yaml

Testing

1.Check if Our Ingress is Updated by AKS

  1. Log in to the Azure portal, go to Application Gateway, and check resources after deploying the application.

Clean Up

1. Remove all resources

Deletes the resource group and associated resources.

az group delete -n demo-weu-rg --yes --no-wait