kuberlr does not support Windows system proxy

[dirk-olmes]

When I'm launching Rancher Desktop it performs some of the steps like the WSL integration etc. but ultimately fails with the error message "kubectl.exe exited with code 255".

In the k8s.log I get the output

Updating release version cache
Ensuring images available for K3s v1.21.5+k3s2
Fetching releases from https://api.github.com/repos/k3s-io/k3s/releases?per_page=100 -> OK
Found old version v1.22.2+k3s2, stopping.
Got 67 versions.
Cache at C:\Users\olmes\AppData\Local\rancher-desktop\cache\k3s is valid.
Waiting for K3s server to be ready on port 6443...
The K3s server is ready on 172.20.102.189:6443.
Updating kubeconfig H:\.kube\config...
Setting default context...
I1021 08:11:26.501228    7428 versioner.go:58] invalid configuration: no configuration has been provided
I1021 08:11:26.597221    7428 versioner.go:64] No local kubectl binary found, fetching latest stable release version
F1021 08:11:56.628190    7428 main.go:62] Get https://storage.googleapis.com/kubernetes-release/release/stable.txt: dial tcp 172.217.16.144:443: i/o timeout

The kubectl.exe that resides in C:\Users\xxx\AppData\Local\Programs\Rancher Desktop\resources\resources\win32\bin seems to be just a wrapper that attempts to download the correct kubectl.exe. Hosts in our environment cannot connect to the internet directly but have to go through a HTTP proxy. It looks like the kubectl.exe does not honor the system's proxy settings since it cannot download the stable.txt.

I have verified that the URL does indeed work using a web browser.

• OS: Windows 10 21H1 Build 19043.928
• Rancher Desktop version 0.6
• Kubernetes version 1.21.5

[dirk-olmes]

OK setting the http_proxy environment variable helped. No idea why it did not work in my attempts before creating this issue.

Going forward it would have been nice if the installer already warned about such issues so that other users don't have to bump their heads against this kind of issues.

[mook-as]

Hi! Thanks for all the details and troubleshooting — I've renamed the issue summary based on my understanding.

We are using kuberlr as the stub to download the appropriate version; I've filed it as flavio/kuberlr#15. I'm still leaving this issue open though, to better handle tracking on our end (e.g. if we decide to schedule time to work on it).