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.

Sign up for GitHub

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

Jump to bottom

[BUG] Argocd bad gateway error #756

Open
eemrdog opened this issue Nov 27, 2024 · 1 comment · Fixed by #757
Open

[BUG] Argocd bad gateway error #756

eemrdog opened this issue Nov 27, 2024 · 1 comment · Fixed by #757
Labels
bug Something isn't working

Comments

@eemrdog
Copy link
Contributor

eemrdog commented Nov 27, 2024

ArgoCD is not accessible giving Bad Gateway error when setting the protocol as http in the provisioning.
Traefik ingress controller could not find the ArgoCD services on the K3s deployment
@eemrdog eemrdog added the bug Something isn't working label Nov 27, 2024
@eemrdog eemrdog linked a pull request Nov 28, 2024 that will close this issue
argocd bad gateway issue fixed with ingress annotations #757
Merged
@eemrdog eemrdog reopened this Dec 2, 2024
@eemrdog
Copy link
Contributor Author

eemrdog commented Dec 2, 2024

the fix with Commit 636f938 did not solve the issue.
Additionally, we should incorporate ingress_flavour instead of kubernetes_flavour parameter to distinguish the ingress class and annotations.
Another thing to fix is to update the annotation for argocd-ingress-grps.yml template file with 'backend-protocol: "GRPC"'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

argocd bad gateway issue fixed with ingress annotations Dynatrace/ace-box
1 participant
@eemrdog