Open debarshibasak opened 5 years ago
@debarshibasak Hi, thanks for opening.
You are right in that chartmuseum does not adhere, and neither does the chart repository API in any way. There is no plan for this to be the case.
However, Helm 3 will be adhering to OCI for distribution, so you can use something like docker/distribution (Docker registry) to host Helm charts.
Please see the Helm 3.0.0-alpha1 release notes for more info: https://github.com/helm/helm/releases/tag/v3.0.0-alpha.1
Hey, sorry if I am asking a naive question. Does that mean both images and charts could possibly reside in the same registry?
@debarshibasak not naive, this stuff is all new. To answer your question - yes. A single registry can be used to host both images and charts, it depends on the what the registry provider allows for. For example, Docker Hub may decide that it only wants to store Docker images.
You are saying the support for docker registry is not on the roadmap? I'm intrested in implement this feature, so i will just fork for now.
@hangyan the support for OCI/registries is on the roadmap for Helm, but not for ChartMuseum. Please see this page: https://helm.sh/docs/topics/registries/
I have create a new project https://github.com/hangyan/chart-registry to use OCI as storage backend. It's kind of interesting
@hangyan interesting idea, to have chartmuseum act as a proxy especially for tools that do not support yet Helm v3 like ArgoCD. any plans to merge this to official Chartuseum repo ?
If somebody wants to submit an "OCI" backend, which converts between APIs, would be happy to review this
Sorry for the later response, @aelbarkani @jdolitsky If you guys are still interested ,would love to create a PR for this.
There is OCI spec for Distribution.
https://github.com/opencontainers/distribution-spec/blob/master/spec.md
I think chartmuseum does not adhere to it. I am just wondering if it is relevant.