Lightning Talk: Helm and the Sigstore Ecosystem
summary
Helm charts can be signed with the built‑in GPG flow using helm package --sign, producing a provenance file that contains the chart.yaml output, the package SHA and the signature. A Sigstore Helm plugin uploads the public key, signature, provenance and hash to Rekor so installs can verify provenance, and OCI charts can be signed at the blob level with cosign. Sigstore also publishes Helm charts to scaffold a full signing/verification stack; adoption of chart signing remains low despite Helm’s ~13,000 contributors.
AI-written summary · about
chapters (11)
- 0:00Intro
- 1:09Ecosystem for Managing Application Delivery
- 1:31What is Helm?
- 2:15Helm Primary Components
- 4:07Signing Helm Charts
- 5:17Helm and Sigstore
- 5:39Helm Sigstore Plugin
- 7:28Signing Helm OCI Artifacts
- 8:11Signing Blobs
- 9:22Sigstore Helm Charts
- 10:15Looking Ahead
related talks
38mHelm: The Charts and the Curious
31mFast & Secure: Package, Sign, Verify, and Deploy
34mIntro: Helm
40mSigstore: How We Started, Where We Are, Where We are Headed
35mHelm: Past, Present, Future
42mHelm Project 2022: How You Can Benefit, Ho...
05mLightning Talk: New Helm Chart Installation Experience with Visual and Repeatable...
23mSecuring Kubernetes Manifests with Sigstore Cosign, What Are Your Options?
