awesome-kubectl-plugins
awesome-kubectl-plugins copied to clipboard
ishantanu
Keep this repo with `krew-index` in sync?
:wave: Hello, maintainer of the kubectl plugin manager krew here.
You are doing great work to collect all these kubectl plugins in this place. What would you think if all of these plugins were also available via krew? This would immediately increase the visibility for the plugins due to krew's large user basis.
However, for us it's hard to track what's going on everywhere in kubectl-land. And we could use your help to keep krew-index up-to-date. So what do you think about opening a new issue in krew-index whenever there is a new addition to the list you maintain here?
Also see https://github.com/kubernetes-sigs/krew-index/issues/349 /cc @ahmetb /cc @ferhatelmas
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.
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 :wink:
@ishantanu As you may be aware, @chriskim06 has implemented custom plugin indices for krew (https://github.com/kubernetes-sigs/krew/issues/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
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.
