-
Notifications
You must be signed in to change notification settings - Fork 923
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
Installation via WinGet #968
Comments
@Bjego: This issue is currently awaiting triage. SIG CLI takes a lead on issue triage for this repo, but any Kubernetes member can accept issues by applying the The 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/test-infra repository. |
Package managers are out of scope as the org just provides binaries and we rely on the community to handle distribution. Personally - I took a look at adding it but it seems that WinGet doesn't yet support standalone executables. Tracking at microsoft/winget-cli#182. Here's the manifest for when that lands.
/close |
@eddiezane: Closing this issue. In response to this:
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/test-infra repository. |
What would you like to be added:
Hey guys, it would be great, if I could install kubectl via WinGet (instead of Scoop or chocolatey) as winget is going to be the official windows based package manager in the future.
Why is this needed:
Win-Get is going to be the official package manager for windows OS. From a corporate perspective it will be much easier to argue for the official packagemanager as for 3rd party software installation sources like choco or scoop.
Why is it better:
Winget is based on simple YAML files to install you software. You do not need to bundle the application in a nuget-package. This makes shipping much easier. It's just an YAML update.
https://docs.microsoft.com/en-us/windows/package-manager/package/repository
The text was updated successfully, but these errors were encountered: