-
Notifications
You must be signed in to change notification settings - Fork 912
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
Argo Rollouts Dashboard unusuable since v1.8.0 #4122
Comments
I am also facing a similar issue where the ingress of the dashboard does not work. It gives a 502 gateway error. ![]() Curl from within the nginx pod gives the error of
Also when we try to do a port-forward on the dashboard pod it fails with the below error
Surprising part is that the command I assume the above command does a port-forwarding on the dashboard pod |
Adding more info from the browser's console
|
Checklist:
Describe the bug
Installation of Argo Rollouts with dashboard using the latest image v1.8.0 breaks completely the UI. I tried using Helm for installation, and I also tried to simply change the imageTag of the dashboard (of an existing working installation using v1.7.2) to v1.8.0 and the effect is the same. By "breaks" I mean that accessing (through port-forward at least) is incredibly slow, and it renders a blank screen with a few words.
To Reproduce
Expected behavior
The dashboard works and I'm able to see things, not a blank screen
Screenshots
Using version v1.7.2

Using version v1.8.0

Version
v1.8.0
Logs
Logs for the entire controller:
Dashboard logs
Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritize the issues with the most 👍.
The text was updated successfully, but these errors were encountered: