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
Running kele-resource and kele-get and possibly others can sometimes hang indefinitely. In at least one case this happens when the test cluster isn't actually running, in which case running kubectl get pods returns:
E0602 12:23:02.053221 8948 memcache.go:265] couldn't get current server API group list: Get "https://127.0.0.1:64890/api?timeout=32s": dial tcp 127.0.0.1:64890: connect: connection refused
E0602 12:23:02.053420 8948 memcache.go:265] couldn't get current server API group list: Get "https://127.0.0.1:64890/api?timeout=32s": dial tcp 127.0.0.1:64890: connect: connection refused
E0602 12:23:02.054579 8948 memcache.go:265] couldn't get current server API group list: Get "https://127.0.0.1:64890/api?timeout=32s": dial tcp 127.0.0.1:64890: connect: connection refused
E0602 12:23:02.055671 8948 memcache.go:265] couldn't get current server API group list: Get "https://127.0.0.1:64890/api?timeout=32s": dial tcp 127.0.0.1:64890: connect: connection refused
E0602 12:23:02.056836 8948 memcache.go:265] couldn't get current server API group list: Get "https://127.0.0.1:64890/api?timeout=32s": dial tcp 127.0.0.1:64890: connect: connection refused
The connection to the server 127.0.0.1:64890 was refused - did you specify the right host or port?
The text was updated successfully, but these errors were encountered:
Running
kele-resource
andkele-get
and possibly others can sometimes hang indefinitely. In at least one case this happens when the test cluster isn't actually running, in which case runningkubectl get pods
returns:The text was updated successfully, but these errors were encountered: