The LoadBalancer type service in Kubernetes on WSL2 should be accessible from both Windows and WSL2.

I encountered an issue in wsl2 ubuntu22.04 while using Kind and its corresponding loadbalancer -- cloud-provider-kind.

I am using Docker Desktop shared between WSL2 and Windows, and I’ve tried both NAT and mirrored WSL2 network configurations.

Notably:

- In NAT mode, cloud-provider-kind needs to be started in privileged mode in WSL2. In this case, the external IP can only be accessed via curl from WSL2, and not from Windows. On Windows, the service can be accessed through localhost with the port kindccm exposing to host machine.
- In mirrored mode: cloud-provider-kind must be started in privileged mode on either Windows or WSL2, along with the --enable-lb-port-mapping=true flag, for the LoadBalancer service to be assigned an external IP. However, the external IP at this point is not accessible—it cannot be accessed from either WSL2 or Windows. service can only be accessed through localhost with the port kindccm exposing to host machine.

Both of these configurations can assign an external IP to a LoadBalancer service. However, is there a way to make the LoadBalancer service accessible directly through the external IP on both WSL2 and Windows, like it is on macOS?

ref:
https://github.com/kubernetes-sigs/cloud-provider-kind
https://github.com/kubernetes-sigs/cloud-provider-kind/issues/189

Start by reproducing the issue with WSL2 Ubuntu 22.04, Kind, and cloud-provider-kind under both NAT and mirrored networking, including --enable-lb-port-mapping=true. Compare access to the assigned LoadBalancer external IP from Windows and WSL2; done means the service is directly reachable from both rather than only through localhost and kindccm's host port.

Written by the indexing model from the issue text.