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

Upgrading and Rolling Back Releases

Use 'helm upgrade' to update deployments and 'helm rollback' to revert to previous versions.

Upgrading and Rolling Back Releases

What you'll learn: How to safely update your Kubernetes deployments with Helm and revert to previous versions when things go wrong.

The Helm Version Control Advantage

Think of Helm releases like save points in a video game. When you upgrade your application, Helm creates a new revision while keeping the old ones. If the new version breaks something, you can instantly jump back to a working state.

Upgrading a Release

Use helm upgrade to deploy a new version of your application. This command updates your existing release with new chart versions, configuration changes, or both:

helm upgrade my-app bitnami/nginx --version 15.0.0

You can also override values during the upgrade:

helm upgrade my-app bitnami/nginx --set replicaCount=5

Helm applies the changes using Kubernetes' rolling update strategy, minimizing downtime. Each upgrade creates a new revision number that Helm tracks automatically.

Rolling Back When Things Break

If an upgrade causes issues, helm rollback restores your previous working state:

# Roll back to the previous revision
helm rollback my-app

# Roll back to a specific revision number
helm rollback my-app 3

You can check your release history to see all revisions:

helm history my-app

This shows revision numbers, update times, status, and descriptions—your complete deployment timeline.

Safe Upgrade Practices

Always test upgrades with --dry-run first to preview changes without applying them. Keep your revision history manageable by setting --max-history to limit stored revisions.

Key Takeaway: Helm's upgrade and rollback commands give you confident deployment control—upgrade fearlessly knowing you can instantly revert to any previous working revision.