Remove Developer Mode / Admin requirement for Windows install by using junctions

[jcrben]

I can and do use WSL, but it's a VM and I'd like to be able to use krew on my host as well (especially since WSL can be finicky and unstable) without convincing the enterprise security folks to turn on Developer Mode for all the developers that I'm trying to enable this for.

I'm not volunteering to do this work, but throwing it out there in response to this comment #631 (comment)

Several CLI applications have undergone a similar shift from symlinks over to junctions on Windows such as:

• fnm - see Windows: Use junctions rather than symlinks Schniz/fnm#519
• volta has an open PR No more symlinks on Windows volta-cli/volta#1552

In the meantime I'm just not using krew on Windows, set up a script to copy the most important plugins over.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[ahmetb]

/lifecycle frozen

[AstralJaeger]

I would really like to see this implemented, as I'm also in a corporate environment where admin access is restricted to a different user.