-
Notifications
You must be signed in to change notification settings - Fork 25
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
Get cluster that doesn't exist gives 502 instead of 404 #133
Comments
Hmm can't reproduce locally. I get the expected:
|
ok I can reproduce in eu-nl-1 |
It seems the nginx-ingress is trying to redirect 404 to the default backend (which it shouldn't) and that fails with
That shouldn't fail either (192.168.0.73 is the default backend) |
the default backend is failing with:
|
Looping in @auhlig |
also in the backend |
It's here |
I cannot |
This has been fixed by deploying #134 |
Trying to get a cluster that doesn't exist anymore (
/api/v1/clusters/bla
) results in a 502 Bad Gateway response now. This should (and used to) return 404 instead.The text was updated successfully, but these errors were encountered: