The ChartMuseum is scheduled to be deprecated in a future v2.4.0 release.

[eugenesotnikov]

I read features of relese 2.2.0. And i was very surprised by this
"The ChartMuseum is scheduled to be deprecated in a future v2.4.0 release."
What does it mean? I didn't find anything about it on site.
We have deploy based on helm+harbor. And i want to be ready for this.

[alxbse]

Not a harbor developer myself but you should probably start looking into using the new OCI artifact support in helm: https://helm.sh/docs/topics/registries/.

Because newer versions of helm can fetch and upload charts in any OCI compliant registry there is no real need for a separate chartmuseum component.

[eugenesotnikov]

i use helm3. But i remember, then i installed harbor without key --with-chartmuseum menu "helm charts" didn't appear in project. And i try understand what developers mean.

[Vad1mo]

Helm 3 uses OCI for package distribution. It ships with two new subcommands to help with this: registry and chart. The registry sub-command handles authentication with OCI registries while chart takes care of save, push and pull charts to the registry.
The fetch and pull sub-commands used for interacting with the chart repositories, chartmuseum, (in earlier versions) are still retained for backward compatibility.

If you use helm 3 then OCI is the future, there is no need for ChartMuseum, so it's safe to deprecate it.

[MaxRink]

If you use helm 3 then OCI is the future, there is no need for ChartMuseum, so it's safe to deprecate it.

This is not true, yet. The default helm behaviour still doesnt support OCI and OCI suppoort is still experimental
A lot of other tooling based upon helm straightup doesnt supoport it at all (fluxv2 for example) as its still experimental and not fully ironed out yet

[sagikazarmark]

Quoting the official website:

Currently OCI support is considered experimental.

This seems to be quite a major change...major enough not to hide it in a changelog.

I also think that most of the ecosystem still uses the "old" helm repository format, so talking about ChartMuseum deprecation seems to be a bit premature to me.

[hojerst]

Considering that Helm Registry support was a major reason why we acutally chose Harbor, I'd also like to see the Chartmuseum supported a bit longer. As mentioned before, the OCI support in helm is still experimental and even needs to be turned on with a env feature flag. I'd really like to see chartmuseum support in Harbor at least until Helm officially supports OCI for production use. Just my two cents.

[Vad1mo]

hey all,

We should close this issue and continue our discussion on #15057

[steven-zou]

Agree with @Vad1mo. If you have any comments on the chartmuseum deprecation work, move to the discussions on #15057.

cc @hojerst / @sagikazarmark / @MaxRink / @eugenesotnikov / @alxbse