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
I`m not sure when the brew dependencies was updated.
But with [email protected]. Kube-ps1 fails to then connect to different clusters.
If I use k9s, I can connect to my servers without issue
However after installing kube-ps1 and hence its dependency, I get the error
Error
E0110 10:40:05.179899 5827 memcache.go:265] couldn't get current server API group list: Get "https://cluster-console.dev.<>/k8s/clusters/local/api?timeout=32s": read tcp 10.1.79.194:50629->10.138.18.238:443: read: socket is not connected
Unable to connect to the server: read tcp 10.1.79.194:50630->10.138.18.238:443: read: socket is not connected
I can:
a) Curl to our server console
b) Use k9s to connect using same .kube config.
Its only if I put in kube-ps1, then connection then fails and its seems its due to dependency.
rgds sanj
The text was updated successfully, but these errors were encountered:
hi
I`m not sure when the brew dependencies was updated.
But with [email protected]. Kube-ps1 fails to then connect to different clusters.
If I use k9s, I can connect to my servers without issue
However after installing kube-ps1 and hence its dependency, I get the error
Error
E0110 10:40:05.179899 5827 memcache.go:265] couldn't get current server API group list: Get "https://cluster-console.dev.<>/k8s/clusters/local/api?timeout=32s": read tcp 10.1.79.194:50629->10.138.18.238:443: read: socket is not connected
Unable to connect to the server: read tcp 10.1.79.194:50630->10.138.18.238:443: read: socket is not connected
I can:
a) Curl to our server console
b) Use k9s to connect using same .kube config.
Its only if I put in kube-ps1, then connection then fails and its seems its due to dependency.
rgds sanj
The text was updated successfully, but these errors were encountered: