Skip to content
RavenstashRavenstashRavenstash

Private Helm OCI registry quickstart

Ravenstash supports Helm charts distributed through OCI. Container and Helm use the same registry hostname while each repository keeps the right package format and dashboard views.

What Ravenstash supports

Section titled “What Ravenstash supports”
  • helm push, pull, show, template, install, and upgrade with OCI references.
  • OCI chart manifests, chart content layers, config objects, and provenance layers.
  • Tags and immutable manifest digests.
  • OCI 1.1 attachments and referrer discovery.
  • Browser views for chart repositories, tags, manifests, blobs, and attachments.

Ravenstash focuses on Helm OCI and does not expose index.yaml, ChartMuseum APIs, or a generic .tgz upload endpoint.

Quick path

Section titled “Quick path”
  1. Create a repository with Helm enabled, or add Helm to an existing repository.
  2. Install Helm and sign in to rvs.
  3. Select the repository with rvs art select platform/deployment-charts.
  4. Package and publish the chart with rvs helm push api-1.2.3.tgz charts.
  5. Pull it with rvs helm pull charts/api --version 1.2.3, or use the same chart path to template or install it.

The examples use:

Repository: deployment-charts
OCI root:   oci://oci.rvsta.sh/platform/deployment-charts/charts
Chart:      api
Version:    1.2.3

Helm appends the chart name during helm push, producing:

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

Version and tag behavior

Section titled “Version and tag behavior”

Helm maps the chart version to an OCI tag. Ravenstash preserves the native tag. Helm’s mapping of + build metadata to _ in tags remains client behavior.

Section titled “Related guides”