Didn’t want to pile into the closed Epic. Just some testing I was able to get done in my env. VPN client that steps on the virtual networks and breaks outbound. wsl-vpnkit had been an imperfect workaround in the past. trying to enable through rdctl shell would give a “UI is busy” comment as w/o a network fix the K3s init phase hangs for about 10min when proxy is in place, but settings.json was updated. Closed/Open and full init completed (no hang on K8s) and confirmed my WSLENV based proxy settings were also in place and active. I have not run though all the implications on forwarding or other day to day activity, but just a note on the gvisor stuff that it is very promising and the fact it works w WSLENV/https_proxy is a big win for us.