what are the updates in helm 3 vs helm 2
- User
what are the updates in helm 3 vs helm 2
- Assistant
Here’s a high-level comparison of what changed from Helm 2 → Helm 3:
Feature Helm 2 Helm 3 Tiller Server-side component (runs in cluster) Removed – client-only, no in-cluster daemon Security & RBAC Tiller needed RBAC permissions Uses your kubeconfig & native RBAC Namespacing Releases cluster-scoped via Tiller Releases are namespace-scoped by default CRD handling CRDs managed via hooks (prone to ordering issues) Built-in CRD support; installerDRY-run logic; CRDs stay installed once appliedChart API & format Chart.yaml apiVersion “v1” Chart.yaml apiVersion “v2” Dependency management requirements.yaml + helm depcommandsMove dependencies into Chart.yaml; helm dependencyunifiedLibrary Charts N/A New “library” chart type for shared templates OCI support No Experimental (v3.7+) native OCI registry push/pull Releases storage ConfigMaps or Secrets in kube-system Secrets by default in release namespace (configurable) Upgrade semver policy Flexible Strict (major version bump in Chart.yaml) Hooks & Tests Basic hooks; helm testlimitedImproved hook ordering; test pods wait for readiness; richer annotations Plugins helm pluginecosystemUnchanged, but better CLI plugin framework CLI UX & commands helm init,helm repo update, etc.Removed init; newhelm registry,helm push(via plugin)Go runtime Go 1.9 → Go 1.12 Go 1.13+ CRD Upgrades Manual Built-in diff & upgrade support for CRDs
More details on the biggest changes:
-
No more Tiller
• Helm 3 eliminated Tiller to simplify security.
• All operations run client-side using your existing kubeconfig. -
Namespace-scoped releases
• In Helm 2, Tiller could “see” the whole cluster; releases were global.
• Helm 3 confines release data (Secrets/ConfigMaps) to the target namespace. -
Chart v2 spec
• Chart.yamlapiVersion: v2→ supports new fields (e.g.dependenciesin Chart.yaml rather than requirements.yaml).
• Breaks backwards compatibility with Kubernetes clusters & Helm 2. -
CRD improvements
• CRDs are installed before any other resources.
• Upgrades detect and patch existing CRDs without deleting custom resources. -
Library charts
• Define reusable template snippets (type: library).
• Other charts canimporthelpers without installing an extra release. -
OCI Image Registry
• Helm can push/pull charts from any OCI-compliant registry (like Docker Hub).
• Encourages artifact signing & provenance tracking. -
Better CLI & UX
• Removal ofhelm init—no more bootstrapping Tiller.
• New commands:helm plugin install,helm get crds,helm registry login, etc.
• Improved output formatting & debugging (--debug,--dry-run). -
Security & Policy
• Uses your existing Kubernetes RBAC.
• No extra cluster-wide privileges needed.
• Release data lives in the app’s namespace by default. -
Strict SemVer for Charts
• You must bump MAJOR version in Chart.yaml for breaking changes.
• Charts can declareappVersion, separate from chart version. -
Testing & Hooks
• More reliable hook ordering (e.g.pre-upgrade,post-upgrade).
•helm testnow waits for pods to become Ready, not just Running.
Emoji TL;DR
✨ No Tiller → simpler & more secure
🔒 Namespace-scoped → least privilege
📦 Chart v2 + OCI → modern packaging
⚙️ Improved CRD & hooks → fewer surprises
🔧 Better CLI → more intuitive commandsFeel free to ask if you want deeper dive into any of these!
-
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.