Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WSL2 support #100

Closed
sky92zwq opened this issue Jul 2, 2024 · 4 comments
Closed

WSL2 support #100

sky92zwq opened this issue Jul 2, 2024 · 4 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@sky92zwq
Copy link

sky92zwq commented Jul 2, 2024

env: wsl2, ubuntu22.04

% go version                 
go version go1.21.4 linux/amd64
% kind version               
kind v0.20.0 go1.21.4 linux/amd64
% kubectl get svc
NAME                            TYPE           CLUSTER-IP      EXTERNAL-IP   PORT(S)               AGE
envoy-default-eg-e41e7b31       LoadBalancer   10.96.164.54    172.18.0.3    80:31407/TCP          5d20h
envoy-gateway                   ClusterIP      10.96.240.27    <none>        18000/TCP,18001/TCP   4d23h
envoy-gateway-metrics-service   ClusterIP      10.96.163.151   <none>        19001/TCP             4d23h

I can see the external-ip, but it will be hang when curl the ip.
% curl 172.18.0.3:80
And I deploy the example from this. It is same.

@aojea aojea added the kind/feature Categorizes issue or PR as related to a new feature. label Jul 2, 2024
@aojea aojea changed the title Can it work in WSL2? WSL2 support Jul 2, 2024
@aojea
Copy link
Contributor

aojea commented Jul 2, 2024

It seems this require some magic with docker microsoft/WSL#4983 (comment)

What version of cloud provider kind are you using?

@sky92zwq
Copy link
Author

sky92zwq commented Jul 3, 2024

It seems this require some magic with docker microsoft/WSL#4983 (comment)

What version of cloud provider kind are you using?

I use go install sigs.k8s.io/cloud-provider-kind@latest, maybe v0.3.0,(I don't find the command of cloud-provider-kind about version)
And I tried the magic, but not success until now.
my ip add shows like:
inet 172.21.225.217/20 brd 172.21.239.255 scope global eth0
the address and the external-ip are Not in the same network segment.
And I found I can't ping the external-ip 172.18.0.3 in WSL2
And I get into the container kindccm-5WRHPD52BKYNVNTNHIULBLNWIR4DMNZ4WECIGO2S , the 172.18.0.3 can be accessed.

@aojea
Copy link
Contributor

aojea commented Jul 17, 2024

should be fixed by #101

@aojea aojea closed this as completed Jul 17, 2024
@sky92zwq
Copy link
Author

sky92zwq commented Jul 19, 2024

works except this old-tiny issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

2 participants