Docs/add wsl2 instructions

[d2461795341]

wsl2 instructions from 189. Hope this is helpful to you.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: d2461795341 / name: Kaijian Ding (3a55825)

[k8s-ci-robot]

Welcome @d2461795341!

It looks like this is your first PR to kubernetes-sigs/cloud-provider-kind 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/cloud-provider-kind has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @d2461795341. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[stmcginnis]

Thanks for improving the docs @d2461795341. Please see the comment about signing the CLA. That will need to be done before this change can be accepted.

Also, if you could edit the PR description to add this line at the end:

Closes: #189 

That will link this PR with that Issue and then GitHub will automatically close it if/when this change is merged.

Thanks!

[aojea]

/ok-to-test
/approve
/assign @stmcginnis

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aojea, d2461795341

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [aojea]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[aojea]

I had feedback that on Windows the tunnel to the IP works #49 , you need to run with admin privileges in order to work runas /user:Administrator IIUIC

[d2461795341]

Earlier, I conducted some further investigations and updated my comments. The support on Windows is not as flawless as on Mac. I created a cluster, started the services, and ran cloud-provider-kind in privileged mode on Windows. However, the external IP has not been assigned. I believe this is a suitable method to allow WSL2 users to access the services on both WSL2 and Windows.

[aojea]

so this windows here means windows and WSL2 at the same time?

[k8s-ci-robot]

PR needs rebase.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.