Azure supports HTTP application routing as an addon (the source code can be found at the following link: https://github.com/Azure/application-gateway-kubernetes-ingress). Earlier, we created the cluster with the http_application_routing under --enable-addons argument argument. AKS would have deployed a set of services to support ingress:

// we could find a set of resources starting with the name addon-http-application-routing-...
# kubectl get pod -n kube-system
NAME READY STATUS RESTARTS AGE
addon-http-application-routing-default-http-backend-6584cdnpq69 1/1 Running 0 3h
addon-http-application-routing-external-dns-7dc8d9f794-4t28c 1/1 Running 0 3h
addon-http-application-routing-nginx-ingress-controller-78zs45d 1/1 Running 0 3h
...

We can reuse the ingress examples from Chapter6. What we have to do is specify annotationkubernetes.io/ingress.class: addon-http-application-routing in the ingress resource and the host name that AKS created for routing your HTTP application. You can find the host name in the addonProfiles.httpApplicationRouting.config.HTTPApplicationRoutingZoneName session when you create or list your cluster, or by using the az aks show --query command to search for it:

// search the routing zone name.
# az aks show --resource-group devops --name myADAKS --query addonProfiles.httpApplicationRouting.config.HTTPApplicationRoutingZoneName
"46de1b27375a4f7ebf30.centralus.aksapp.io"