This message was deleted.
# rancher-desktopa
adamant-kite-43734
03/01/2023, 7:46 AMThis message was deleted.
f
fast-garage-66093
03/01/2023, 7:50 AMIf you disable administrative access (so you don't get a bridged interface), then the node ip should be fixed at
192.168.5.15fast-garage-66093
03/01/2023, 7:51 AMAssuming this is about macOS (or Linux); doesn't apply on Windows
l
late-train-67842
03/01/2023, 12:08 PMWindows đ
w
wide-mechanic-33041
03/01/2023, 12:50 PMbecause WSL2 sets the /20 dynamically the subnet for the nodes will change as well. i know for the no_proxy I am hoping that connections just move to a rancher.local DNS model which would allow for the no_proxy to adapt w/o config changes. I am also watching for https://github.com/curl/curl/pull/9775 which should come when wsl-distro is updated to 3.17 from the current 3.16
wide-mechanic-33041
03/01/2023, 12:51 PMthan you can just add the rfc1918s to WSLENV and whatever ICS elects you should be good
wide-mechanic-33041
03/01/2023, 1:50 PMi did tweak /etc/apk/repositories and did an update/upgrade which does seem to work as i wanted with basic curl testing via rdctl shell, but the âstarting kubernetesâ phase still hangs. I am using wsl-vpnkit at the same time which I think is related so looking forward to 1.8 release for the built in test feature.
wide-mechanic-33041
03/01/2023, 2:02 PMi am also poking at request.js (love that a 3y deprecated work still gets 20mil weekly downloads) as the exception points at that (http when expecting https tells me its trying to proxy) but vpnkit abstraction does make those routes a bit funny in the host (kubectl)
wide-mechanic-33041
03/01/2023, 2:17 PMyeah I had to update my kubeconfig to localhost:6443 because of the lack of registered routes due to vpnkit abstraction
l
late-train-67842
03/03/2023, 8:08 AMThx for the infos
16 Views