Course contentsShow
← Cloud and Infrastructure
Lesson 1555 of 2,98931. Helm Package ManagerFree lesson

Chart Signing and Provenance

Sign charts with GPG keys and verify provenance to ensure chart authenticity and integrity.

Chart Signing and Provenance

What you'll learn: How to cryptographically sign Helm charts and verify their authenticity to ensure you're deploying trusted, unmodified packages.

Why Sign Charts?

When you download a Helm chart from a repository, how do you know it hasn't been tampered with? Chart signing uses GPG (GNU Privacy Guard) keys to create a cryptographic signature—think of it like a tamper-evident seal on medication. If the seal is broken, you know something's wrong.

How Chart Signing Works

When you package a chart, you can sign it with your private GPG key:

helm package --sign --key 'your-key-name' --keyring ~/.gnupg/secring.gpg mychart/

This creates two files:

  • mychart-1.0.0.tgz (the chart archive)
  • mychart-1.0.0.tgz.prov (the provenance file)

The .prov file contains the chart's cryptographic hash and signature, proving who created it and that it hasn't been altered.

Verifying Provenance

Users can verify a chart before installation:

helm install myrelease mychart-1.0.0.tgz --verify --keyring ~/.gnupg/pubring.gpg

Helm checks:

  1. The signature matches the public key
  2. The chart's hash matches what's in the provenance file
  3. The signer is trusted

If verification fails, Helm refuses to install—protecting you from malicious or corrupted charts.

Practical Considerations

You need a GPG key pair configured beforehand. The signing process integrates into your chart packaging workflow, while verification happens during installation or chart inspection.

Key Takeaway: Chart signing with GPG keys creates cryptographic proof of authenticity and integrity, allowing users to verify charts haven't been tampered with before deploying them to production clusters.