-
Notifications
You must be signed in to change notification settings - Fork 109
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
Add sample krew plugin manifest #2
Comments
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/lifecycle frozen |
@soltysh has brought up this idea: why don't we have also include a Krew (https://sigs.k8s.io/krew) plugin manifest in this plugin sample?
To do this, we would need to:
Provide a prebuilt archive file containing cross-platform binaries of this repo (since this program is in Go) on GitHub releases section (or somewhere else on the internet).
Provide a command to built this archive file locally (
make
orhack/build-plugin-package.sh
)Add a
sample-plugin.yaml
to the root, that's pinning to a particular tag of the binary release archive and its sha256 sum (since we can't update those values as part of the release easily).Once we do these, anyone cloning this repository can try the sample manifest like:
make
orhack/build-plugin-package.sh
kubectl krew install --archive out/archive.tar.gz --manifest sample-plugin.yaml
The text was updated successfully, but these errors were encountered: