Keynote: Getting to Know Helm 3
summary
Helm 3 replaces Tiller so the client talks directly to the Kubernetes API and stores release metadata as namespace-scoped secrets; upgrades use a 3-way strategic merge (old manifest, new manifest, live state) to avoid losing injected sidecars. Charts move to apiVersion v2 with dependencies in Chart.yaml, support library charts and JSON Schema value validation, and put CRDs in a crds/ directory with helm-2 compatibility hooks. OCI registry support is available as an OCI registry experiment behind an env var, and a helm-2to3 plugin migrates configs and releases (dry-run supported).
AI-written summary · about
chapters (7)
- 0:00What is Helm
- 1:40Helm 3 commands
- 3:34Helm architecture
- 5:20Helm 3 upgrades
- 6:19New features
- 7:56CRTs
- 9:22Experiments
