You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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?
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
orcivo 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?This is while using
Civo CLI v1.0.41
on an Intel Mac.The text was updated successfully, but these errors were encountered: