This message was deleted.

@fast-garage-66093 ☝️ 🙏

I wish I knew... @calm-sugar-3169 any ideas?

I’m not 100% sure what is going on by looking at this. How do I repro this?

Thanks guys. Quite easy to repro. Reset Rancher (Facotry setting) and reinstall with any version of Kubernetes, I have tried different versions ranging from 1.20.x to 1.28.6. Once cluster is ready, run

kubectl run -it --rm --restart=Never busybox --image=busybox:1.28 -- nslookup kubernetes.default

, you will see dns resolution does not work. Issue is limited to DNS within the cluster. Rancher desktop can do outside-cluster resolution, so issue is not with

/ect/resolve.conf

Any pod that needs to connect to another pod times out. Standalone pods are fine i.e. no dependies on other pods. Some context, I had same issue two weeks ago..... after spending hours trying to fix, out of despiration, I applied

Networking Tunnel

option under WSL, then it worked. All interpod communication were good and pods were running sucessfully. Two days ago, I tried to spin up my environment, noticed I was back to square one 😩 . This time

Neworking Tunnel

had no effect, instead with error

level=fatal msg="no default routes found in \"/proc/net/route\" or \"/proc/net/ipv6_route\""

Also with Tunnelling enabled, the installation (setup) gets stuck at

Updating Kubeconfig

perpetually. But once

Neworking Tunnel

, is disabled, it installs successfully but lack dns pod resolution persists. Thanks guys.@fast-garage-66093 @calm-sugar-3169