Hey Team! I am seeing an odd issue when i have rancher desktop open (with or without kubernetes started) my requests to kubernetes clusters seem to take an extra 5 seconds and i always get the following errors with kubectl

W0810 11:11:09.918791   30466 transport.go:243] Unable to cancel request for *exec.roundTripper
I0810 11:11:09.919551   30466 versioner.go:56] Remote kubernetes server unreachable

running kubectl with verbose i see

W0810 11:11:40.870288   30615 transport.go:243] Unable to cancel request for *exec.roundTripper
I0810 11:11:40.870416   30615 versioner.go:56] Remote kubernetes server unreachable
I0810 11:11:40.942818   30615 loader.go:372] Config loaded from file:  /Users/bobby_work/.kube/config
I0810 11:11:40.949541   30615 round_trippers.go:466] curl -v -XGET  -H "Accept: application/json;as=Table;v=v1;g=<http://meta.k8s.io|meta.k8s.io>,application/json;as=Table;v=v1beta1;g=<http://meta.k8s.io|meta.k8s.io>,application/json" -H "User-Agent: kubectl1.23.5/v1.23.5 (darwin/amd64) kubernetes/c285e78" '<https://teleport-proxy-fa453aa96721d1b9.elb.us-west-2.amazonaws.com:3026/api/v1/pods?limit=500>'
I0810 11:11:46.026591   30615 round_trippers.go:495] HTTP Trace: DNS Lookup for <kubernetesapi> resolved to [{54.202.178.200 } {35.81.43.116 }]
I0810 11:11:46.106126   30615 round_trippers.go:510] HTTP Trace: Dial to tcp:<kubernetesapi_ip>:3026 succeed
I0810 11:11:46.342400   30615 round_trippers.go:570] HTTP Statistics: DNSLookup 5034 ms Dial 79 ms TLSHandshake 85 ms ServerProcessing 150 ms Duration 5392 ms

when i quit out of rancher desktop I dont see the remote kubernetes server unreachable errors and the DNSLookup time is fast

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