Application-gateway-kubernetes-ingress: Better way to prohibit changes to multiple targets

[pbloigu]

Is your feature request related to a problem? Please describe.
We have 3 clusters behind an app gw. Each cluster has multiple hosts exposed. For each cluster I now have to create ProhobitedTargets for each of the hostnames in the other two clusters. This is a bit cumbersome.

Describe the solution you'd like
I would be fine with either of the two solutions:

1. Allow for automatically prohibiting changes to hostnames not present in the current cluster
2. Allow specifying multiple hostnames for a ProhibitedTarget, preferably with a regular expression

[3quanfeng]

Hi @pbloigu , are all of your 3 clusters are AKS clusters?

[pbloigu]

Hi @pbloigu , are all of your 3 clusters are AKS clusters?

Yes they are. Do you have a better approach in mind to achieve what I described that already works with AGIC as it is? I would love to hear about it as I'm in the midst setting up the environments right now. Changing the environment later on will be harder as they're in active use.

[3quanfeng]

No, you will have to configure the prohibited policy on each of the cluster, or you could use one appgw per cluster without any prohibited targets?

[pbloigu]

Yeah, that would incur additional costs which I'm unable to accept at this time. However, the host names are stable and once defined there won't be any new ones, so this is a one time task and I can live with it. In any case, though, the ability to specify multiple hosts for a ProhibitedTarget would be a nice feature to add, I think.

[derkoe]

We want to use one application gateway for multiple teams/AKS clusters. One team does not know which URLs the other teams use. For this use case and generally for an easier configuration it would be great to have AzureIngressAllowedTargets with wildcards that can be defined per cluster.

[aelmanaa]

Hello,

any milestone to deliver this feature? we have exactly the same need as @pbloigu