Package your chart locally: `helm package ./mychart` — this produces a `.tgz` archive
Push the chart to GHCR: `helm push mychart-<version>.tgz oci://ghcr.io/YOUR_ORG` — Helm stores it as an OCI artifact under the chart name and version as the tag
Pull and install from OCI: `helm install myrelease oci://ghcr.io/YOUR_ORG/mychart --version <version>`
List available versions by querying the GHCR package API or using `crane ls ghcr.io/YOUR_ORG/mychart` (from the crane CLI)
Known gotchas
OCI-based Helm repositories do not support `helm repo add` or `helm search repo` — consumers must reference charts by full OCI URI and know the version in advance or query the registry API separately
GHCR packages are private by default; make the package public in GitHub package settings or ensure all consumers authenticate before pulling
Helm does not yet support index-based discovery for OCI registries — if you need searchable chart catalogs, maintain a separate traditional HTTP chart index alongside OCI pushes
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp