AppGW is being provisioned by AGIC within a Kubernetes Helm deployment script. I need a way to manage more than 100 custom listeners, or more than one appgw pointed at the same k8s cluster.
#AppGW HTTP Listener Limitation of 100, possible solutions or workarounds.
zealous tree
mild river
I'm not aware of a way to have more than one application gateway as an ingress controller to the same cluster, and I think the 100 active listeners on an application gateway is a hard limit - more details here: https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/azure-subscription-service-limits#application-gateway-limits
You could try running an alternative ingress controller, e.g. NGINX, or perhaps you could consider splitting your workloads across more than one cluster?
zealous tree
Hmm yeah those are both options. Wait a single cluster can't have more than one appgw period, or more than one that is configured using AGIC @mild river
mild river
Hmm yeah those are both options. Wait a single cluster can't have more than one ...
A cluster can have more than one ingress controller, if you are using something like NGINX (example here: https://learn.microsoft.com/en-us/azure/aks/app-routing-nginx-configuration), but I don't think the same holds true if you are using application gateway for your ingress controller.
[EDIT] This might be possible with application gateway, if you can split your workloads across multiple namespaces within the cluster? There is an example on GitHub issues here: https://github.com/Azure/application-gateway-kubernetes-ingress/issues/831. They had an issue due to naming, but it looks like they were able to overcome it, if you read right to the bottom of the issue.