This message was deleted.

We do ship

kuberlr

to handle fetching the correct version of

kubectl

(actually,

kubectl

in our configuration is really a symlink to

kuberlr

); so it sound like it's trying to contact what it thinks is the correct kubernetes cluster and timing out. But that should have nothing to do with whether Rancher Desktop is running… How is your

kubeconfig

etc set up? Anything interesting to make

kuberlr

pick up the wrong thing?

i use teleport and when i login it will generate a kubeconfig for me