Support Helm charts from OCI registries

[squaremo]

The language in the Helm docs about registries suggests that the plan is support using OCI (https://helm.sh/docs/topics/registries/). This feature still experimental in Helm, but it looks like the plan is to graduate it in a release soon: helm/helm#7613, helm/community#136.

[fredgate]

Yes it would be a really great feature. OCI is the future for Helm chart, and Harbor already support replication to external registries like Azure Container Registry.

[hiddeco]

The OCIGetter was made available in Helm v3.5.0 but has not been extensively documented yet.

Update: no chances of integration yet, as the registry.Client required to pull it all off (🥁) is still in helm/internal.

[LittleChimera]

The OCIGetter was made available in Helm v3.5.0 but has not been extensively documented yet.

Update: no chances of integration yet, as the registry.Client required to pull it all off (🥁) is still in helm/internal.

Isn't it enough to just use OCIGetter which wraps the client you mention?

[hiddeco]

No, it is not as we do not have access to the RegistryClient that is injected using the options. We are therefore unable to construct the OCIGetter properly.

[Jimmy-Newtron]

I have browsed for few days searching a solution to have my Charts stored in a private GitLab container registry (OCI compliant registry) and be finally able to pull those charts from the usual Helm command.

I have found the code from two small projects that looks appealing:

• https://github.com/alauda/oci-chartrepo
• https://github.com/hangyan/chart-registry

The goal is to build a classic Chart registry from the content of the OCI registry using the following endpoints:

• /index.yaml # Get the OCI data from --storage-registry-repo, then transform them into standard chart repository data structures.
• /charts/:name # Download a chart artifact

Do you think that such solution can be the good direction to avoid rewriting a specific module to handle OCI registries?

[alxy]

Is there any timeline available on when this might become available? We are also using Azure Container registry and MSFT is suggesting to use OCI with Helm3, which on the Helm side is considered experimental.
Now that we did the migration we also wanted to look into GitOps/Flux, however, its a major blocker now that I cannot pull the charts from the registry, as OCI3 is not supported.

[hiddeco]

See: helm/helm#9188 (comment)

[rchrd]

@alxy It is also possible to push tar.gz files of Helm chart to an ACR. We currently push both the OCI and the tar.gz, for now we only use the tar.gz with Flux but when OCI is available when can just switch without the need to push all charts again.