Back to Cheatsheets Hub
DevOps & Orchestration
Updated for 2026

Helm Package Manager Cheatsheet

Helm CLI commands including chart creation, deployments, release upgrades, rollbacks, and template debugging.

Target Version Compatibility

Interactive Skill Mastery

Mark commands as learned to build your customized reference tracker. Retained locally in this browser.

Level:Novice
Command Mastery Progress0 of 19 Mastered (0%)

Repository & Search

helm repo add <name> <url>
BeginnerBasics
Add an external Helm chart repository to your local CLI index.

When to Use

When packaging, installing, or upgrading Kubernetes applications using chart blueprints and resource definitions.

Common Mistakes

Applying deployments without dry-running Helm charts first, which can cause resource conflicts inside Kubernetes namespaces.

Shortcut / Pro-Tip

Use `helm template --debug` to render and inspect the raw Kubernetes YAML resource files before running installs.

Example

helm repo add <name> <url>

Output Example

Console / Terminal
Release successfully deployed and tracked in Helm list.
helm repo update
BeginnerBasics
Sync latest charts and versions from all registered remote repositories.

When to Use

When packaging, installing, or upgrading Kubernetes applications using chart blueprints and resource definitions.

Common Mistakes

Applying deployments without dry-running Helm charts first, which can cause resource conflicts inside Kubernetes namespaces.

Shortcut / Pro-Tip

Use `helm template --debug` to render and inspect the raw Kubernetes YAML resource files before running installs.

Example

helm repo update

Output Example

Console / Terminal
Release successfully deployed and tracked in Helm list.
helm search repo <keyword>
BeginnerBasics
Search through your registered chart repositories for a specific application chart.

When to Use

When packaging, installing, or upgrading Kubernetes applications using chart blueprints and resource definitions.

Common Mistakes

Applying deployments without dry-running Helm charts first, which can cause resource conflicts inside Kubernetes namespaces.

Shortcut / Pro-Tip

Use `helm template --debug` to render and inspect the raw Kubernetes YAML resource files before running installs.

Example

helm search repo <keyword>

Output Example

Console / Terminal
Release successfully deployed and tracked in Helm list.

Install & Upgrade

helm install <release-name> <chart-name> --values values.yaml
BeginnerBasics
Install a Kubernetes application release with custom values from a file.

When to Use

When packaging, installing, or upgrading Kubernetes applications using chart blueprints and resource definitions.

Common Mistakes

Applying deployments without dry-running Helm charts first, which can cause resource conflicts inside Kubernetes namespaces.

Shortcut / Pro-Tip

Use `helm template --debug` to render and inspect the raw Kubernetes YAML resource files before running installs.

Example

helm install <release-name> <chart-name> --values values.yaml

Output Example

Console / Terminal
Release successfully deployed and tracked in Helm list.
helm upgrade <release-name> <chart-name> --set replicaCount=3
BeginnerBasics
Upgrade an existing application release and override values inline.

When to Use

When packaging, installing, or upgrading Kubernetes applications using chart blueprints and resource definitions.

Common Mistakes

Applying deployments without dry-running Helm charts first, which can cause resource conflicts inside Kubernetes namespaces.

Shortcut / Pro-Tip

Use `helm template --debug` to render and inspect the raw Kubernetes YAML resource files before running installs.

Example

helm upgrade <release-name> <chart-name> --set replicaCount=3

Output Example

Console / Terminal
Release successfully deployed and tracked in Helm list.
helm upgrade --install <release-name> <chart-name> --values values.yaml
BeginnerBasics
Idiomatic single command to upgrade a deployment or install it if it does not yet exist.

When to Use

When packaging, installing, or upgrading Kubernetes applications using chart blueprints and resource definitions.

Common Mistakes

Applying deployments without dry-running Helm charts first, which can cause resource conflicts inside Kubernetes namespaces.

Shortcut / Pro-Tip

Use `helm template --debug` to render and inspect the raw Kubernetes YAML resource files before running installs.

Example

helm upgrade --install <release-name> <chart-name> --values values.yaml

Output Example

Console / Terminal
Release successfully deployed and tracked in Helm list.
helm install <release-name> <chart-name> --wait --timeout 10m
BeginnerBasics
Block the command until all deployed pods and services enter healthy states or timeout.

When to Use

When packaging, installing, or upgrading Kubernetes applications using chart blueprints and resource definitions.

Common Mistakes

Applying deployments without dry-running Helm charts first, which can cause resource conflicts inside Kubernetes namespaces.

Shortcut / Pro-Tip

Use `helm template --debug` to render and inspect the raw Kubernetes YAML resource files before running installs.

Example

helm install <release-name> <chart-name> --wait --timeout 10m

Output Example

Console / Terminal
Release successfully deployed and tracked in Helm list.
helm rollback <release-name> <revision>
AdvancedRecovery
Instantly rollback an active deployment release to a specified prior version.

When to Use

When packaging, installing, or upgrading Kubernetes applications using chart blueprints and resource definitions.

Common Mistakes

Applying deployments without dry-running Helm charts first, which can cause resource conflicts inside Kubernetes namespaces.

Shortcut / Pro-Tip

Use `helm template --debug` to render and inspect the raw Kubernetes YAML resource files before running installs.

Example

helm rollback <release-name> <revision>

Output Example

Console / Terminal
Release successfully deployed and tracked in Helm list.
helm uninstall <release-name>
BeginnerBasics
Permanently delete and clean up a release and all of its associated cluster resources.

When to Use

When packaging, installing, or upgrading Kubernetes applications using chart blueprints and resource definitions.

Common Mistakes

Applying deployments without dry-running Helm charts first, which can cause resource conflicts inside Kubernetes namespaces.

Shortcut / Pro-Tip

Use `helm template --debug` to render and inspect the raw Kubernetes YAML resource files before running installs.

Example

helm uninstall <release-name>

Output Example

Console / Terminal
Release successfully deployed and tracked in Helm list.

Releases & Status

helm list --all-namespaces
BeginnerBasics
Display all Helm release deployments across all Kubernetes cluster namespaces.

When to Use

When packaging, installing, or upgrading Kubernetes applications using chart blueprints and resource definitions.

Common Mistakes

Applying deployments without dry-running Helm charts first, which can cause resource conflicts inside Kubernetes namespaces.

Shortcut / Pro-Tip

Use `helm template --debug` to render and inspect the raw Kubernetes YAML resource files before running installs.

Example

helm list --all-namespaces

Output Example

Console / Terminal
Release successfully deployed and tracked in Helm list.
helm status <release-name>
IntermediateDebugging
Fetch the real-time status, deployed pods, and notes of a specific release.

When to Use

When packaging, installing, or upgrading Kubernetes applications using chart blueprints and resource definitions.

Common Mistakes

Applying deployments without dry-running Helm charts first, which can cause resource conflicts inside Kubernetes namespaces.

Shortcut / Pro-Tip

Use `helm template --debug` to render and inspect the raw Kubernetes YAML resource files before running installs.

Example

helm status <release-name>

Output Example

Console / Terminal
Release successfully deployed and tracked in Helm list.
helm history <release-name>
BeginnerBasics
Fetch revision history, dates, descriptions, and statuses for an active release.

When to Use

When packaging, installing, or upgrading Kubernetes applications using chart blueprints and resource definitions.

Common Mistakes

Applying deployments without dry-running Helm charts first, which can cause resource conflicts inside Kubernetes namespaces.

Shortcut / Pro-Tip

Use `helm template --debug` to render and inspect the raw Kubernetes YAML resource files before running installs.

Example

helm history <release-name>

Output Example

Console / Terminal
Release successfully deployed and tracked in Helm list.
helm get values <release-name> --all
BeginnerBasics
Retrieve and display all overridden active deployment values for a running release.

When to Use

When packaging, installing, or upgrading Kubernetes applications using chart blueprints and resource definitions.

Common Mistakes

Applying deployments without dry-running Helm charts first, which can cause resource conflicts inside Kubernetes namespaces.

Shortcut / Pro-Tip

Use `helm template --debug` to render and inspect the raw Kubernetes YAML resource files before running installs.

Example

helm get values <release-name> --all

Output Example

Console / Terminal
Release successfully deployed and tracked in Helm list.

Debugging & Templates

helm template <chart-path> --debug
IntermediateDebugging
Compile and render Helm templates locally to inspect generated YAML manifests before deploying.

When to Use

When packaging, installing, or upgrading Kubernetes applications using chart blueprints and resource definitions.

Common Mistakes

Applying deployments without dry-running Helm charts first, which can cause resource conflicts inside Kubernetes namespaces.

Shortcut / Pro-Tip

Use `helm template --debug` to render and inspect the raw Kubernetes YAML resource files before running installs.

Example

helm template <chart-path> --debug

Output Example

Console / Terminal
Release successfully deployed and tracked in Helm list.
helm lint <chart-path>
IntermediateDebugging
Perform a static syntax check on your custom Helm chart directories for potential errors.

When to Use

When packaging, installing, or upgrading Kubernetes applications using chart blueprints and resource definitions.

Common Mistakes

Applying deployments without dry-running Helm charts first, which can cause resource conflicts inside Kubernetes namespaces.

Shortcut / Pro-Tip

Use `helm template --debug` to render and inspect the raw Kubernetes YAML resource files before running installs.

Example

helm lint <chart-path>

Output Example

Console / Terminal
Release successfully deployed and tracked in Helm list.
helm test <release-name>
IntermediateDebugging
Invoke and execute assertion pods declared within your Helm templates to verify deployment health.

When to Use

When packaging, installing, or upgrading Kubernetes applications using chart blueprints and resource definitions.

Common Mistakes

Applying deployments without dry-running Helm charts first, which can cause resource conflicts inside Kubernetes namespaces.

Shortcut / Pro-Tip

Use `helm template --debug` to render and inspect the raw Kubernetes YAML resource files before running installs.

Example

helm test <release-name>

Output Example

Console / Terminal
Release successfully deployed and tracked in Helm list.

Chart Creation

helm dependency update <chart-path>
BeginnerBasics
Rebuild, download, and align external sub-chart dependencies declared in Chart.yaml.

When to Use

When packaging, installing, or upgrading Kubernetes applications using chart blueprints and resource definitions.

Common Mistakes

Applying deployments without dry-running Helm charts first, which can cause resource conflicts inside Kubernetes namespaces.

Shortcut / Pro-Tip

Use `helm template --debug` to render and inspect the raw Kubernetes YAML resource files before running installs.

Example

helm dependency update <chart-path>

Output Example

Console / Terminal
Release successfully deployed and tracked in Helm list.
helm package <chart-path> --destination ./dist
BeginnerBasics
Compile and archive your custom chart folder into a shareable Gzipped tarball.

When to Use

When packaging, installing, or upgrading Kubernetes applications using chart blueprints and resource definitions.

Common Mistakes

Applying deployments without dry-running Helm charts first, which can cause resource conflicts inside Kubernetes namespaces.

Shortcut / Pro-Tip

Use `helm template --debug` to render and inspect the raw Kubernetes YAML resource files before running installs.

Example

helm package <chart-path> --destination ./dist

Output Example

Console / Terminal
Release successfully deployed and tracked in Helm list.
helm create <chart-name>
BeginnerBasics
Generate a boilerplate directory structure for building a custom Helm chart.

When to Use

When packaging, installing, or upgrading Kubernetes applications using chart blueprints and resource definitions.

Common Mistakes

Applying deployments without dry-running Helm charts first, which can cause resource conflicts inside Kubernetes namespaces.

Shortcut / Pro-Tip

Use `helm template --debug` to render and inspect the raw Kubernetes YAML resource files before running installs.

Example

helm create <chart-name>

Output Example

Console / Terminal
Release successfully deployed and tracked in Helm list.

Helm Best Practices

1Perform Dry-Runs Prior to Deployment

Never push raw charts. Run helm template or helm upgrade --dry-run --debug to compile and inspect raw rendered YAML configurations locally before deploying.

2Isolate Environment Configuration Files

Separate settings by keeping dedicated environment files (e.g. values-dev.yaml, values-prod.yaml) to maintain environment hygiene.

3Establish Strict Timeout Limits

Integrate wait and timeout flags (e.g. --wait --timeout 10m) inside deployments to block and rollback instantly if Pods enter CrashLoopBackOff.

4Declare Chart Dependencies Explicitly

List child sub-charts under the dependencies array inside Chart.yaml. Execute helm dependency update to download and lock dependency archives.

5Integrate Automated Deployment Checks

Implement automated Helm tests (e.g. helm test) containing assertion Pods to verify post-installation endpoint health.

Common Helm Errors & Solutions

Error

Error: UPGRADE FAILED: timed out waiting for the condition

Solution

Kubernetes failed to transition Pods to running states (e.g. bad images or probes). Check Pod logs using: kubectl describe pods.

Error

Error: another operation (install/upgrade/rollback) is in progress

Solution

A prior Helm deployment crashed or hung, locking the release state. Force unlock by deleting the Helm lease secret or wait for the release lock timeout.

Error

Error: validation failed: immutable field cannot be updated

Solution

Certain Kubernetes resources (like StatefulSet volume mappings or Job specifications) are immutable. Uninstall the release or manually patch the resource.

Error

Error: failed to parse values.yaml: yaml: line 12: did not find expected key

Solution

Your overrides file contains invalid indentation or syntax. Locate the line with an online YAML linter or execute: helm lint <chart-path>.

Error

Error: connection refused or missing kubernetes context

Solution

The Helm CLI is unable to reach your cluster. Verify your KUBECONFIG environment variable or test cluster access using: kubectl cluster-info.

Common Helm Interview Questions

Q1What is Helm and how does it benefit Kubernetes deployments?

Helm is the package manager for Kubernetes. It abstracts raw YAML configurations by packaging related cluster manifests into a template-driven 'Chart'. This permits parameterization, versioning, automated dependency management, and atomic rollbacks of whole application deployments.

Q2Explain the relationship between templates/ directory, values.yaml, and Chart.yaml.

templates/ contains parameterized Kubernetes resource templates (Service, Deployment, etc.). values.yaml defines the default configurations and parameter overrides. Chart.yaml stores key metadata such as chart version, description, and dependency definitions.

Q3How does Helm track releases and rollback to prior versions?

Helm stores release metadata and state history inside Secret resources directly in the target Kubernetes namespace. When you run 'helm rollback <release> <revision>', Helm reads that specific historical secret state and executes an upgrade patch to restore it.

Q4What is the difference between a Helm Chart version and an App version?

The Chart Version (defined under 'version' in Chart.yaml) dictates the version of the Helm package template itself. The App Version (defined under 'appVersion') indicates the version of the actual application container image being deployed.

Q5How do you manage external sub-chart dependencies in Helm 3?

Dependencies are declared in the 'dependencies' array directly inside Chart.yaml (naming the chart, version, and repository URL). Running 'helm dependency update' downloads these charts into the 'charts/' directory as locked archives.

Related Resources

Tool

REST API Tester

Test API routes and endpoints directly in your browser with full request controls.

Tool

JSON Formatter & Validator

Beautify, validate, and minify JSON structures instantly.

Article

Best Free Online Developer Tools

An expert review of must-have online utilities for developers.

Cheatsheet

Git Cheatsheet

Essential command reference for local and remote version control repositories.