Install a chart with Helm
QuenchWorks charts publish to GHCR as OCI artifacts. There is no Helm repository to add and no account to create. You need Helm 3.8 or newer (OCI support is on by default from 3.8.0).
Install
Install a chart by its OCI reference. Swap redis for any chart and the version shown on its page:
helm install my-redis oci://ghcr.io/quenchworks/charts/redisPin the chart version so an upgrade is something you do on purpose, not a surprise:
helm install my-redis oci://ghcr.io/quenchworks/charts/redis --version 0.0.5Configure
Auth is on by default. The chart generates a password into a Secret on first install. To set your own, or to create an application database where the chart supports it, pass values:
helm install my-redis oci://ghcr.io/quenchworks/charts/redis \ --set auth.password='change-me'For anything beyond a value or two, use a file:
helm install my-redis oci://ghcr.io/quenchworks/charts/redis -f my-values.yamlEach chart ships a values.schema.json, so Helm validates what you pass before it renders anything. See Configuration for the persistence, resources, scheduling, and security-context keys that every chart shares.
Inspect before you install
Pull the values and the rendered manifests without touching the cluster:
helm show values oci://ghcr.io/quenchworks/charts/redis --version 0.0.5helm template my-redis oci://ghcr.io/quenchworks/charts/redis --version 0.0.5Verify before you install
Charts are OCI artifacts, so cosign verifies them by tag the same way it verifies an image:
cosign verify ghcr.io/quenchworks/charts/redis:0.0.5 \ --certificate-identity-regexp 'https://github.com/quenchworks/.+' \ --certificate-oidc-issuer https://token.actions.githubusercontent.comA valid result prints the workflow that built the chart and its Rekor log entry. To verify a specific build instead of the tag, pass an @sha256:... digest. See Verify a signature and Pin by digest.
Upgrade and roll back
Upgrade to a newer chart version with the same reference:
helm upgrade my-redis oci://ghcr.io/quenchworks/charts/redis --version 0.0.6If something looks wrong, roll back to the previous revision:
helm rollback my-redisUninstall
helm uninstall my-redisHelm leaves PersistentVolumeClaims behind on purpose so your data survives a reinstall. Delete them by hand if you want the storage back.
Next steps
- Configuration: persistence, resources, scheduling, and security context.
- Pin by digest: run exactly what was scanned and signed.
- Air-gapped install: relocate charts and images into a private registry.