Any plan to support cloud hosted helm repo

[warjiang]

with the help of oci spec, many clouder provider with container registry service also provide service of hosted charts for enterprise, for example:

google cloud: https://cloud.google.com/artifact-registry/docs?hl=en alibaba cloud: https://www.alibabacloud.com/help/en/acr/developer-reference/api-references/?spm=a2c63.p38356.0.0.35be7b02yTDKNx

however helm will fetch index.yaml from repo, but the provider will not serve index.yaml directly, with openapi or sdk, we can construct index.yaml indirectly.

so any plan to support this feature, with options like --cloud-provider=gcp/alibaba and more

[gjenkins8]

Helm supports OCI registries: https://helm.sh/docs/topics/registries/

[warjiang]

Helm supports OCI registries: https://helm.sh/docs/topics/registries/

@gjenkins8 Yes, with oci feature supported, you can push charts to registry, but if you execute helm repo add command, it will return

Error: looks like "xx" is not a valid chart repository or cannot be reached: failed to fetch xx/index.yaml : 404 Not Found

The root cause is when you add repo, it will execue

when it execute DownloadIndexFile, will generate url with index.yaml, and use http client to fetch it,

But the provider i mentioned above donot provide index.yaml file directly, but provider provide sdk, with help of sdk, we can generate file same as index.yaml

[warjiang]

that's what i want to supported, if specify the registry provider, we can change the default logic to fetch index.yaml, instead of fetch index.yaml directly, we can use sdk gen index.yaml, maybe it can be implemented in other way 🍭

[yxxhero]

@gjenkins8 good question.

[gjenkins8]

@warjiang I'm still not really understanding what is being asked for. It is correct that helm repo add doesn't work for OCI registries, but it also isn't necessary.

Why do you want/need to add an OCI registry as a "helm repo"? What functionality would that bring?

[warjiang]

@warjiang I'm still not really understanding what is being asked for. It is correct that helm repo add doesn't work for OCI registries, but it also isn't necessary.

Why do you want/need to add an OCI registry as a "helm repo"? What functionality would that bring?

because after add repo, user can use helm search repo {repoName}. If as you described above, oci feature only be designed to push/pull chart, may be it should have third party tools to do it, or it can be a helm plugin or others.

[github-actions[bot]]

This issue has been marked as stale because it has been open for 90 days with no activity. This thread will be automatically closed in 30 days if no further activity occurs.