This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(310.4, 18%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESP%3C/text%3E%3C/svg%3E)
Hello everyone, I was creating an AKS cluster and I noticed that the Azure portal changed a lot and the main thing is that now once the AKS Cluster has been created and there is no option to create the application gateway in the Networks option.
Now I had to create it manually using a command.
Has anyone else noticed this? They went from being able to create the appgw in a super simple way to a difficult one >=/
Or is there an easy way to create it like it was before?
Hello @Sebastian Pacheco
Yes, you're correct that the Azure portal has changed and the option to create an application gateway for an AKS cluster is no longer available in the "Networks" section. However, there are still several ways to create an application gateway for your AKS cluster.
One way is to use the Azure CLI to create the application gateway. You can use the following command to create an application gateway with the AKS ingress controller:
az network application-gateway create --name <appgw-name> --resource-group <resource-group-name> --location <location> --sku Standard_v2 --capacity <capacity> --http-settings-cookie-based-affinity Disabled --frontend-port 80 --http-settings-port 80 --http-settings-protocol Http --public-ip-address <public-ip-name> --vnet-name <vnet-name> --subnet <subnet-name> --servers <server-name> --aks-zone-redundant true
This command creates an application gateway with the Standard_v2 SKU, a specified capacity, and the AKS ingress controller enabled. You can customize the command to fit your specific needs.
Another way to create an application gateway for your AKS cluster is to use the Azure portal to create a new application gateway resource and then configure it to work with your AKS cluster. This involves creating a new application gateway resource, configuring the backend pool to point to your AKS cluster, and configuring the listener and rules to route traffic to your AKS cluster.
I hope this helps! Let me know if you have any further questions.
If I have answered your query, please click "Accept as answer" as a token of appreciation
A shame, instead of simplifying the tasks, they make them more difficult... what I did was this:
(I had already created my AKS Cluster from the portal, therefore the gateway is not created automatically)
1.- Deploy a new application gateway
az network public-ip create -n myPublicIp -g MC_xxxxxxxxx --allocation-method Static --sku Standard
az network vnet create -n myVnet -g MC_xxxxxxxxx --address-prefix 10.0.0.0/16 --subnet-name mySubnet --subnet-prefix 10.0.0.0/24
az network application-gateway create -n myApplicationGateway -g
MC_xxxxxxxxx
2.- Enable the AGIC plugin on the existing AKS cluster via the Azure CLI:
appgwId=$(az network application-gateway show -n myApplicationGateway -g homa-rg-aks-vm -o tsv --query "id")
az aks enable-addons -n myCluster -g homa-rg-aks-vm -a ingress-appgw --appgw-id $appgwId
After these steps I still couldn't access my website, error 502 appeared (and the gateway threw a timeout when trying to reach the pod) and it was because I still needed to pair the 2 subnets so that the gateway could have access to my AKS
3.- Then pair both subnets (AKS and GW) from the portal
And with those steps I managed to get the appgw up and communicate with my pods.
Thanks!
Thank you for the feedback, I will pass on the same to product team. If you have any specific feedback related to the portal please feel to write at feedback.azure.com
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more