From 3ad88aaad42434a07a1645f4c07895adab102155 Mon Sep 17 00:00:00 2001 From: Phil Dibowitz Date: Thu, 14 Mar 2024 00:12:01 -0700 Subject: [PATCH] Update for custom krew index (#13) Signed-off-by: Phil Dibowitz --- README.md | 20 ++++++++++++++++---- 1 file changed, 16 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index bf3b407..5100215 100644 --- a/README.md +++ b/README.md @@ -109,8 +109,13 @@ the binary (`kubectl-d`) in your PATH. If you get an error like "macOS cannot verify this app..." see [this page]( https://zaiste.net/os/macos/howtos/resolve-macos-cannot-be-opened-because-the-developer-cannot-be-verified-error/). -We've submitted this plugin to Kraw, and will update these installation -instructions once that's merged. +If you are a [Krew](https://krew.sigs.k8s.io/) user, we maintain our own index, +which you can use to install `kubectl-daemons`: + +```shell +kubectl krew index add jaymzh https://github.com/jaymzh/jaymzh-krew.git +kubectl krew install kubectl-d +``` ## Building from source @@ -160,6 +165,13 @@ Ideally, plugins would be a library that could hook into various stages within kubectl and allow you to not have to implement so much yourself, but it turns out that's not how kubectl plugins work. -**Will you be submitting this to Krew?** +**Why do you maintain your own Krew index?** + +Krew +[felt](https://github.com/kubernetes-sigs/krew-index/pull/3679#issuecomment-1987113765) +this plugin wasn't sufficiently different from what you could do with `kubectl` +options and as such did not accept it. -Yes! That'll happen very soon. +However, a custom krew index is a simple [git +repository](https://github.com/jaymzh/jaymzh-krew), so maintaining our own +isn't an issue.