Publish and install Helm OCI charts

Use rvs helm with the exact namespace/repository target. The wrapper supplies temporary authentication for that Helm repository.

Package and push

rvs art select platform/deployment-charts
rvs helm package ./charts/api

rvs helm push api-1.2.3.tgz charts

Omit charts to push directly into the selected repository root. A nested destination such as team/backend is also supported. Helm appends the chart name and version from its metadata; the destination must not include either. The resulting chart reference is:

oci://oci.rvsta.sh/platform/deployment-charts/charts/api:1.2.3

When a provenance file is present, use Helm’s normal provenance workflow. Ravenstash stores the resulting OCI graph without claiming that the provenance has been independently verified.

Pull or inspect

rvs art select platform/deployment-charts
rvs helm pull charts/api --version 1.2.3

rvs helm show chart charts/api --version 1.2.3

Template, install, and upgrade

rvs art select platform/deployment-charts
rvs helm template api charts/api --version 1.2.3

rvs helm upgrade --install api charts/api --version 1.2.3 \
  --namespace api --create-namespace

Pin an immutable chart manifest digest where your deployment process requires a content-stable reference. Tags remain mutable selectors.

Reference rules

Short chart paths resolve inside the selected repository for pull, install, upgrade, show, and template. Use --version for a version or version range; without it, Helm chooses the version using its normal rules.

Full oci://host/... references and HTTP chart URLs keep their meaning. Local charts need an explicit path such as ./api, ../api, or an absolute path; .tgz archive paths also stay local. A bare name resolves privately even when a directory with that name exists.

An alias such as bitnami/nginx also means a private chart path in rvs helm. Use plain helm for configured public repository aliases, or supply an explicit --repo https://... URL. Private misses never fall back to a public registry.

Dependencies

Helm resolves OCI chart dependencies using the dependency repository declared in Chart.yaml. Keep full oci:// repository URLs in Chart.yaml; shorthand does not rewrite dependency files. All Ravenstash dependencies must belong to the selected repository. Public dependencies retain their own URLs and credentials.

Troubleshooting

• Confirm the selected Ravenstash repository supports Helm, not Container.
• Pass a destination directory to rvs helm push, or omit it for the selected repository root; Helm adds the chart name itself.
• Do not append a classic Helm index.yaml path.
• Ravenstash does not look for missing charts in public Helm or OCI registries.