Support for OCI Helm registries

[antonlisovenko]

Hi

Thanks for this amazing tool. Helm OCI registries is a new fashion now, most of container registries (ECR, Quay) support this format so it's quite convenient to publish the internal company Helm charts there and avoid the need to create a new Helm repository.

The way it's implemented in Helmsman for example is using the format oci://my-registry.local/my-chart (https://github.com/Praqma/helmsman/blob/master/docs/how_to/helm_repos/oci.md)

Are there plans to support OCI Helm in Devspace?

thank you /kind feature

[FabianKramm]

@antonlisovenko thanks for creating this issue! Since this is just the chart name, did you try to use something like:

deployments:
- name: test
  helm:
    chart:
      name: oci://my-registry.local/my-chart

As this would be translated to helm install oci://my-registry.local/my-chart, which might already work?

[hendrikheil]

@FabianKramm I just looked into this for devspace v6. The install command works perfectly like that. There is a somewhat annoying workflow issue with authentication against Helm OCI Registries at the moment. Helm doesn't respect --username and --password for those commands just yet. So currently you can have one of these solutions:

1. Configure normal docker registry authentication (alias ~/.docker/config.json) for the registry
2. Login with helm registry login before you use devspace
3. Have devspace v6 make a local config file to use with upgradeArgs and templateArgs by supplying --registry-config /path

All of them aren't really declarative in any way. If https://github.com/helm/helm/issues/10881 gets resolved there would be no need to touch devspace at all. But still might be worth considering adding helm chart registries for v6.1 in case that feature doesn't land in Helm?