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
AGIC is already installed using helm.
Make an update using the helm upgrade command.
The URL will fail with 502 Bad Gateway error.
To Reproduce
Steps to reproduce the behavior:
Create an update using the following helm command: helm upgrade ingress-azure -f helm-config.yaml application-gateway-kubernetes-ingress/ingress-azure -n agic-ns
Then query the AzureIngressProhibitedTargets
kubectl get AzureIngressProhibitedTargets -A
NOTE: You will notice that the prohibit-all-targets is present in the same namespace.
Ingress Controller details
Output of kubectl describe pod <ingress controller> . The pod name can be obtained by running helm list.
Output of `kubectl logs .
Any Azure support tickets associated with this issue.
The text was updated successfully, but these errors were encountered:
Describe the bug
AGIC is already installed using helm.
Make an update using the helm upgrade command.
The URL will fail with 502 Bad Gateway error.
To Reproduce
Steps to reproduce the behavior:
Create an update using the following helm command:
helm upgrade ingress-azure -f helm-config.yaml application-gateway-kubernetes-ingress/ingress-azure -n agic-ns
Then query the AzureIngressProhibitedTargets
kubectl get AzureIngressProhibitedTargets -A
NOTE: You will notice that the prohibit-all-targets is present in the same namespace.
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: