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

Delay & 502 error with civo kubernetes ls #286

Closed
emrul opened this issue Nov 16, 2022 · 2 comments
Closed

Delay & 502 error with civo kubernetes ls #286

emrul opened this issue Nov 16, 2022 · 2 comments

Comments

@emrul
Copy link

emrul commented Nov 16, 2022

Hi, if I run civo kubernetes ls on its own I get back my cluster in my region (London) as expected.

If I then try civo kubernetes ls --region nyc1 or civo kubernetes ls --region fra1 it appears to hang for a while before throwing a 502 error. It may be because I have no resources in either region but in that case I'd expect 0 results rather than an error?

# civo kubernetes ls --region nyc1
Error: ResponseDecodeFailed: failed to decode the response expected from the API - status: 502 Bad Gateway, code: 502, reason: <html>
<head><title>502 Bad Gateway</title></head>
<body>
<center><h1>502 Bad Gateway</h1></center>
<hr><center>nginx</center>
</body>
</html>

This is while using Civo CLI v1.0.41 on an Intel Mac.

@emrul
Copy link
Author

emrul commented Nov 17, 2022

Further update on this, I created a cluster in nyc1 and the command civo kubernetes ls --region nyc1 worked fine. Interestingly, I then deleted the cluster and the same command continued to work (returning 0 results as expected, no error).

However, civo kubernetes ls --region fra1 still times out and throws out a 502. I suspect, you guys are initialising something when a cluster is first created in a region, even if the cluster is then removed?

So, suggested repro step: use a new Civo account.

@alessandroargentieri
Copy link
Member

we had a performance issue that we fixed. It should be solved now! Thanks for reporting @emrul

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