Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Helm

The Helm provider tracks chart versions from both classic HTTP chart repositories (an index.yaml served under the repo URL) and OCI registries (oci://, where a chart’s versions are the repository’s tags).

# clover: provider=helm registry=https://charts.bitnami.com/bitnami chart=nginx constraint=minor
version: 18.2.0

Keys

KeyDescription
providerhelm
registryThe chart source. An https:// (or http://) URL is a classic repository, while an oci:// URL is an OCI registry base.
chartThe chart name (e.g. nginx). A bare name, since the repository path belongs in registry.
constraintHow far the version may move (major/minor/patch, or a semver range)
includeKeep only matching versions
excludeDrop matching versions
prereleaseAllow or exclude prerelease versions
cooldownRequire a minimum age before a version is eligible (classic repositories only, see below)

Classic vs OCI

The registry scheme selects how Clover looks up versions:

  • Classic (https://). Clover fetches <registry>/index.yaml and reads the named chart’s published versions. The index carries each version’s release date, so cooldown applies, and the chart-tarball checksum, which a follower can source without a download.
  • OCI (oci://). Clover lists the chart’s tags from the registry. OCI tags carry no dates, so cooldown does not apply. Pass --deep if a chart has more tags than fit on one page.
# clover: provider=helm registry=oci://registry-1.docker.io/bitnamicharts chart=nginx constraint=minor
version: 18.2.0

Checksums and digests

A classic repository’s index publishes the chart-tarball checksum, so a follower can render it alongside the version:

# clover: provider=helm registry=https://charts.bitnami.com/bitnami chart=nginx id=chart constraint=minor
version: 18.2.0
# clover: from=chart value=sha256 pattern=*.tgz
digest: 0000000000000000000000000000000000000000000000000000000000000000

For an oci:// chart, Clover resolves the manifest digest, so a value=sha256 pin stays fresh.

Authentication

Classic repositories are usually public. For a private OCI chart registry, run helm registry login (or docker login), or set CLOVER_HELM_TOKEN, and Clover reuses those credentials.