• k8s
• AzureAKS
• ApplicationGateway-Sucks

k8s/AzureAKS/ApplicationGateway - Sucks

• 2022 Implemented Kubernetes AKS cluster with add-on application GW
  • Azure installs controller to replace ingress functionality with Azure Application GW.

Why does using "Application Gateway" as ingress for AKS suck ?

1. It does not uses k8s services but tries to map directly to container ip's
2. Application GW liveness proves uses the default ingress path prefix, ignoring the livenessProves for the container.

   • Causes pod serving /api through ingress to fail if it returns 404 for /api & /api/. but works for /api/myfunction.

   • Have to manually edit the "Health proves" in the azure portal.
3. After redeployment of pods where their ip's update it is real slow to update to new container IP's.