You can now publish and manage Helm charts in Cloudsmith using modern OCI-based workflows. Charts pushed via Helm V3 to our OCI-compatible registry are correctly identified in the UI and supported through a new dedicated endpoint: helm.oci.cloudsmith.io. These improvements build on our full support for OCI v1.1 compliance and make adopting Helm’s latest distribution model easier.
🚀 What's Changed
Previously, Cloudsmith offered a Docker registry at docker.cloudsmith.io that was fully compliant with the OCI v1.1 standard. While users could push any OCI artifact to this registry, non-Docker artifacts were still displayed as Docker packages, making it harder to work with and manage your artifacts. Now, both OCI-compliant and traditional (non-OCI) Helm charts are supported and clearly labeled in the UI, providing better visibility and smoother workflows.
Try it out
Here’s how to push a chart using Helm’s OCI support:
# add and update a helm repo + download a sample chart
helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx
helm repo update
helm pull ingress-nginx/ingress-nginx
# list the chart
ls ingress-nginx-4.12.3.tgz
# Login to your OCI-compliant Helm repository in Cloudsmith
helm registry login helm.oci.cloudsmith.io -u USERNAME -P PASSWORD
# Push the chart
helm push ingress-nginx-4.12.3.tgz oci://helm.oci.cloudsmith.io/OWNER/REPOSITORY
While Cloudsmith OCI Registries are GA, our Helm OCI registry is in Early Access, so some Cloudsmith features like Helm OCI Upstreams aren't yet available. Please, contact Support if you want to try it out.