Skip to content
TheChatArchiveThe Chat Archive
o4-mini-2025-04-16· OpenAIHugging Face LMArena Human Preference 140K

what are the updates in helm 3 vs helm 2

From a Chatbot Arena battleThe same person sent this prompt to two anonymous models at once. Compare it with Qwenqwen3-235b-a22b-no-thinking’s answer.
  1. User

    what are the updates in helm 3 vs helm 2

  2. Assistant

    Here’s a high-level comparison of what changed from Helm 2 → Helm 3:

    FeatureHelm 2Helm 3
    TillerServer-side component (runs in cluster)Removed – client-only, no in-cluster daemon
    Security & RBACTiller needed RBAC permissionsUses your kubeconfig & native RBAC
    NamespacingReleases cluster-scoped via TillerReleases are namespace-scoped by default
    CRD handlingCRDs managed via hooks (prone to ordering issues)Built-in CRD support; installer DRY-run logic; CRDs stay installed once applied
    Chart API & formatChart.yaml apiVersion “v1”Chart.yaml apiVersion “v2”
    Dependency managementrequirements.yaml + helm dep commandsMove dependencies into Chart.yaml; helm dependency unified
    Library ChartsN/ANew “library” chart type for shared templates
    OCI supportNoExperimental (v3.7+) native OCI registry push/pull
    Releases storageConfigMaps or Secrets in kube-systemSecrets by default in release namespace (configurable)
    Upgrade semver policyFlexibleStrict (major version bump in Chart.yaml)
    Hooks & TestsBasic hooks; helm test limitedImproved hook ordering; test pods wait for readiness; richer annotations
    Pluginshelm plugin ecosystemUnchanged, but better CLI plugin framework
    CLI UX & commandshelm init, helm repo update, etc.Removed init; new helm registry, helm push (via plugin)
    Go runtimeGo 1.9 → Go 1.12Go 1.13+
    CRD UpgradesManualBuilt-in diff & upgrade support for CRDs

    More details on the biggest changes:

    1. No more Tiller
      • Helm 3 eliminated Tiller to simplify security.
      • All operations run client-side using your existing kubeconfig.

    2. 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.

    3. Chart v2 spec
      • Chart.yaml apiVersion: v2 → supports new fields (e.g. dependencies in Chart.yaml rather than requirements.yaml).
      • Breaks backwards compatibility with Kubernetes clusters & Helm 2.

    4. CRD improvements
      • CRDs are installed before any other resources.
      • Upgrades detect and patch existing CRDs without deleting custom resources.

    5. Library charts
      • Define reusable template snippets (type: library).
      • Other charts can import helpers without installing an extra release.

    6. OCI Image Registry
      • Helm can push/pull charts from any OCI-compliant registry (like Docker Hub).
      • Encourages artifact signing & provenance tracking.

    7. Better CLI & UX
      • Removal of helm init—no more bootstrapping Tiller.
      • New commands: helm plugin install, helm get crds, helm registry login, etc.
      • Improved output formatting & debugging (--debug, --dry-run).

    8. Security & Policy
      • Uses your existing Kubernetes RBAC.
      • No extra cluster-wide privileges needed.
      • Release data lives in the app’s namespace by default.

    9. Strict SemVer for Charts
      • You must bump MAJOR version in Chart.yaml for breaking changes.
      • Charts can declare appVersion, separate from chart version.

    10. Testing & Hooks
      • More reliable hook ordering (e.g. pre-upgrade, post-upgrade).
      • helm test now 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 commands

    Feel free to ask if you want deeper dive into any of these!

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.