This message was deleted.
# rancher-desktop
a
This message was deleted.
f
I'm not sure if we will get to it in time for 1.6. One focus area will be to get port forwarding to the external IP working on Windows. Unlike on macOS the port forwarding is currently limited to localhost.
👍 1
We are certainly aware that proxy support needs some serious work, and having completed the new preference dialog (and internal corresponding changes, which were quite a bit larger than you'd expect), I think we are at a place now where we can also make the corresponding UI settings possible without too much effort.
w
yup switching from the IPs to some internal DNS schema will take some work 100%. WSL2 just makes it extra hard to do the no_proxy because of the dynamically elected subnet for WSL
honestly getting proxies into the runtime i have been fine with for a while, but it’s the impact on the intra cluster flows that has been my biggest challenge. I see a mess of errors on Mac from metrics etc, but for WSL it just errors out
f
I know we have several proxy issues on Github, but is there one that describes your situation properly?
w
https://github.com/rancher-sandbox/rancher-desktop/issues/2147 is the biggest on my radar. The others I have docs for and while UX can be improved my folks are always used to the occasional workaround, but I have yet to figure out how to workaround this one.
f
I've put in on the "Next" milestone, so at least we are going to look at it during triage meetings. Doesn't mean we will get to it, as there is probably 3 times as much stuff assigned to the milestone than what there is time for, so there will be a lot of pruning going on over the following weeks
👍 1
w
yup moving the intra cluster traffic to a model that allows for a simple no_proxy is going to take a bit of work so even scoping it out has value. enjoy the break!