-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Publish HelmCharts as OCI (Open Container Initative) format #74
Comments
thanks for the issue. we have talked about this but it's not a priority and would first require a bit of prep work. would you mainly be interested in the device plugins stuff or some other helm charts as well? |
I understand, for me personally the charts intel-device-plugins-operator and intel-device-plugins-gpu would be nice. |
>[!IMPORTANT] > After this is merged and charts are released you will need to make the packages public from [here](https://github.com/orgs/intel/packages) I also bumped some deps and replaced ACCESS_TOKEN secret with the builtin GITHUB_TOKEN Fixes: intel#74
I see what you mean by prep work, why are some charts folders being duplicated when a new chart version is made? |
Description
Publish the helm charts as OCI, example to the intel docker hub, quay or GHCR?
Context
OCI is becoming more prevalent, example some of our dependencies like bitnami charts are also as OCI:
blog.bitnami.com/2023/04/httpsblog.bitnami.com202304bitnami-helm-charts-now-oci.html
In particular bitnami is deprecating the index.yaml and way and strongly suggest we migrate to OCI.
Possible Solution
My suggestion is to push as OCI as additional step (keeping existing way). If all goes well then we can also add some time frame and then start pushing new versions to OCI only. We need not disable the existing index.yaml as that would break users.
The text was updated successfully, but these errors were encountered: