https://rancher.com/ logo
Title
l

late-train-67842

03/01/2023, 7:46 AM
is there a way to permanently set the master node ip of k3s of rancher-desktop? So i could add it to the NO_PROXY variables? FACTORY RESET -> FRESH INSTALL (fixed IP)
f

fast-garage-66093

03/01/2023, 7:50 AM
If you disable administrative access (so you don't get a bridged interface), then the node ip should be fixed at
192.168.5.15
. That means you will only be able to reach the node via port-forwarding from the host though.
Assuming this is about macOS (or Linux); doesn't apply on Windows
l

late-train-67842

03/01/2023, 12:08 PM
Windows 😄
w

wide-mechanic-33041

03/01/2023, 12:50 PM
because 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
than you can just add the rfc1918s to WSLENV and whatever ICS elects you should be good
i 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.
i 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)
yeah 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 AM
Thx for the infos