Is this useful?

[hasheddan]

I wrote k8scr quickly as a way to get OCI images into registries running in Kubernetes clusters because it was relevant to work I do with Crossplane. However, I imagine it could be generally useful for folks, and some have already shown interest. There are a variety of ways the scope of this project could be expanded, such as making the in-cluster registry component a little more automated (i.e. automatically deploy tiny temporary registry just to get image to whatever its final destination in the cluster is). Anyway, I am happy to expand / maintain this project if folks find it useful, so I would love to get some feedback as to what people want to see and how they may be using it already. Feel free to comment below or, if necessary, reach out privately to @hasheddan.

[Vad1mo]

I am contributing to Harbor and there is a demand to have a distributed registry with one central unit where everyone can push to and satellites to pull images from. Something like a proxy cache and something that can distribute images. The idea is not to have a full-blown registry but something that can offload the central registry and improve the reliability of the entire system.

[hasheddan]

@Vad1mo sounds interesting! Are you imagining the "satellites" as pull-only then?

[Vad1mo]

@Vad1mo sounds interesting! Are you imagining the "satellites" as pull-only then?

yes, but I must admit I am biased as I only see what customer demand, not other potential use cases. There are also P2P solutions out there that I didn't try yet.

IMO these are the top 3 use cases for a satellite concept:

1. Improved availability and reliability of the entire container distribution system for pulling images.
2. Less data traffic
3. Speed
4. Distribute images to clusters with limited internet access