Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

After upgrade using helm, AGIC is unable to update Application Gateway. #1651

Open
thuwas opened this issue Oct 3, 2024 · 1 comment
Open

Comments

@thuwas
Copy link

thuwas commented Oct 3, 2024

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.
@sromero1avanade
Copy link

This solved the problem I was experiencing

kubectl delete AzureIngressProhibitedTarget prohibit-all-targets -n <namespace_of_agic>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants