Keep this repo with `krew-index` in sync? about awesome-kubectl-plugins HOT 6 OPEN

@ishantanu As you may be aware, @chriskim06 has implemented custom plugin indices for krew (kubernetes-sigs/krew#566). This opens an opportunity for independent collections of kubectl plugins. You could now offer your curated list of kubectl plugins as a krew index, and simplify installation for everyone. See https://krew.sigs.k8s.io/docs/user-guide/custom-indexes/ for how it's done.

The core k8s.sigs.io/krew-index will continue to be curated by the krew folks, but it's likely we will reject plugins more often now (e.g. when plugins have too much overlap, or there are naming issues). Nevertheless, it would be good to have a more liberal collection which has a smaller entry barrier. This gap could be filled by your repository, if you want to take up this work.

cc @ahmetb @chriskim06

from awesome-kubectl-plugins.

Perfect! It's good to know that you are also keeping an eye open for additions to krew. Don't forget to involve the plugin authors 😉

from awesome-kubectl-plugins.

Read https://krew.sigs.k8s.io/docs/developer-guide/custom-indexes/

from awesome-kubectl-plugins.

Hi @corneliusweig. Agreed. This sounds like a nice idea. I will make sure to create a new issue in krew-index when I add new plugins to the list.

from awesome-kubectl-plugins.

Hi @corneliusweig. This sounds like a very good idea. I looked at the custom-indexes documentation and while it was quite straightforward to understand, it didn't mention the repository structure required for other repositories to be used as indexes. I presume it should be similar to krew-index's structure (i.e. having a plugin directory inside a repository which contains plugin yaml's)?

This is a welcome addition to krew, and I can surely work on making this plugin list available for installation via krew.

from awesome-kubectl-plugins.

That answers everything, thanks.

from awesome-kubectl-plugins.