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

Helm Versioning and Chart Versions

Understand semantic versioning for charts and how to install specific chart versions.

Helm Versioning and Chart Versions

You'll learn how Helm uses semantic versioning to track chart releases and how to install specific versions for predictable deployments.

Understanding Chart Versions

Every Helm chart has two version numbers that matter:

  1. Chart version — The version of the packaging itself (bumped when templates or structure change)
  2. App version — The version of the application being deployed (e.g., nginx 1.21.0)

Think of it like a cookbook analogy: the chart version is which edition of the cookbook you're using, while the app version is which recipe (software version) you're actually cooking.

Semantic Versioning in Action

Helm charts follow semantic versioning (SemVer): MAJOR.MINOR.PATCH

  • MAJOR (1.x.x): Breaking changes to the chart structure
  • MINOR (x.2.x): New features, backward-compatible
  • PATCH (x.x.3): Bug fixes only

When you run helm search repo nginx, you see the latest versions. But you can install a specific version:

# Install latest version
helm install my-nginx bitnami/nginx

# Install specific chart version
helm install my-nginx bitnami/nginx --version 13.2.1

# List all available versions
helm search repo nginx --versions

Why Version Control Matters

Installing specific versions ensures reproducibility. If version 14.0.0 introduces breaking changes but you need stability, pin to 13.2.1 across all environments. This prevents "it worked yesterday" surprises when the latest chart changes unexpectedly.

You can also upgrade to a specific version:

helm upgrade my-nginx bitnami/nginx --version 13.2.5

Key Takeaway: Helm charts use semantic versioning to track changes—always specify --version in production to avoid unexpected updates and maintain deployment consistency across environments.