Proposal nr.2: Support for custom index repositories

[chriskim06]

Allowing users to specify custom indices to download plugins from would allow people to distribute plugins without having to go through the main krew-index repo. This would be useful at companies where people want to share plugins that are specific to their workflows or aren't appropriate for krew-index.

I wanted to share the proposal doc I had thrown together here https://docs.google.com/document/d/1Im5gmBA6yuKRWgJWbaBjTTFNvkH0me05V3wEeNPU7fE/edit?usp=sharing and opened a new issue for it based on this. There's a lot of similarities to the docs in #23 so if this doesn't add enough I'd be happy to close this.

A lot of ideas came from https://docs.brew.sh/Taps, mainly around how to handle duplicate plugin names.

[ahmetb]

Thanks for writing this up.
I'm calling this "proposal number two" for index repos, as you've said there are similarities.
I think both Cornelius and I should read both how Taps work and how your design works. It might take some time but hang in there.
/kind proposal

[ahmetb]

/assign

[corneliusweig]

@chriskim06 can you ping me on kubernetes slack?

[ahmetb]

Ahead of our online meeting about this on Feb 18th, I've documented my wishlist of what I'd love to see from the solution + implementation process:

https://docs.google.com/document/d/1_xYsxtwtQTboKOyp920pb1OWLTQEdU6gF7-QvUA6S0Y/edit?usp=sharing

[chriskim06]

Sounds good I'll take a look through that doc and add comments if I have any questions

[ahmetb]

Both @corneliusweig and @ahmetb (myself) have discussed the proposal with @chriskim06 and approved it.

[jdolitsky]

Late to the game here, but would like to point to #580 regarding alternative approach to distribution via OCI

[jdolitsky]

The fact that this issue has come up is actually itself testament to "why use OCI" - all these concepts (multitenancy, distributed repos, auth) have already been solved for in the context of Docker push/pull which is the basis for OCI distribution-spec: https://github.com/opencontainers/distribution-spec

[jdolitsky]

and yes, I realize this throws a big wrench into the existing plan and architecture, but I feel very strongly this is the correct way forward, especially for tooling in the k8s/container space. feel free to reach out to discuss more.

[ahmetb]

@jdolitsky let's move the discussion there as it doesn't concern this feature.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[ahmetb]

/lifecycle frozen

[chriskim06]

Should we close this one too?

[ahmetb]

👍🏼
/close

[k8s-ci-robot]

@ahmetb: Closing this issue.

In response to this:

👍🏼
/close

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.