You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
We have an app gateway that is shared for an entire AKS cluster. When a team accidentally references a WAF policy that doesn't exist yet, it breaks the app gateway backend connections for the entire App Gateway, and not for the ingress in question.
To Reproduce
Steps to reproduce the behavior:
Create an AKS cluster
Create 2 applications to run on the cluster, one using no WAF policy and one using a WAF policy that doesn't exist yet
Both applications fail to resolve IP addresses from the backend pool.
The issue is there and will break the whole AKS ingresses created, after one of the ingress rules would have non-existing WAF rule reference.
Yes, this is what we experienced. We are working with a CSA on this, but there doesn't seem to be any good solutions. Waiting to hear back more and can update this issue if I do
Describe the bug
We have an app gateway that is shared for an entire AKS cluster. When a team accidentally references a WAF policy that doesn't exist yet, it breaks the app gateway backend connections for the entire App Gateway, and not for the ingress in question.
To Reproduce
Steps to reproduce the behavior:
Create an AKS cluster
Create 2 applications to run on the cluster, one using no WAF policy and one using a WAF policy that doesn't exist yet
Both applications fail to resolve IP addresses from the backend pool.
Example ingress:
Ingress Controller details
kubectl describe pod <ingress controller
> . The pod name can be obtained by runninghelm list
.The text was updated successfully, but these errors were encountered: