This message was deleted.
# rancher-desktop
a
This message was deleted.
s
I did confirm that removing rancher-desktops kubectl from my path and installing kubectl manually resolves the slowness issue
I would like to use the kubectl version installed with rancher-desktop 😕
w
did you set your context in kubectl using use-context?
s
yea i did
i did it for both rancher's kubernetes and our gke cluster
i also noticed simply doing kubectl --help was slow
w
its a binary so not sure on the "slow"
s
i saw a github issue mentioning the rancher-desktop wraps kubectl with some utility that does some apiserver + kubectl compatibility checking or something
that is what i thought bout rancher-desktop is doing something when you execute kubectl.exe
w
so the stub for RD just calls into the VM and runs that one i believe. so maybe that is the delay you are seeing? you could always use the native kubectl calling into the cluster.
p
Yeah, our
kubectl.exe
is actually kuberlr which pings the API server to figure out the version and downloads a close-enough version of
kubectl
internally. Sounds like that's having issues, but that uses the same API as the real CLI, so that isn't expected…