This is an ingress controller that can be run on Azure Kubernetes Service (AKS) to allow an Azure Application Gateway to act as the ingress for an AKS cluster.
AzureIngressProhibitedTarget deployed (on prod AKS cluster indicated DNS name for non-prod and vise versa)
Both clusters having the same Ingress and Service definitions. This resulted in a single backend pool and backend target in the app gw, while there should've been obviously two backend targets and two backend pools (one of each for each of the two clusters).
App geteway has one backend pool, with two rules , but with one backend target (IP belongs to the ingress of the second AKS)
To Reproduce
Configure shared App Gateway via HELM
Deploy on each cluster pod, service with the same name and namespace.
Deploy Ingress on each cluster.
Go to App Gateway UI and check backend pools
Instead of two backend pools will be created only one with two rules and one target (looks like due to identical pod\service\namespace names on each AKS )
Describe the bug
Both clusters having the same Ingress and Service definitions. This resulted in a single backend pool and backend target in the app gw, while there should've been obviously two backend targets and two backend pools (one of each for each of the two clusters).
Ingress Prod:
Ingress Non-prod:
App geteway has one backend pool, with two rules , but with one backend target (IP belongs to the ingress of the second AKS)
To Reproduce
Ingress Controller details
AKS Non-prod
AKS Prod
AKS PROD