-
Notifications
You must be signed in to change notification settings - Fork 362
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
Remove Developer Mode / Admin requirement for Windows install by using junctions #843
Labels
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
Comments
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/lifecycle frozen |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
In the meantime I'm just not using krew on Windows, set up a script to copy the most important plugins over.
The text was updated successfully, but these errors were encountered: