Helm Charts Kubernetes: Essential Commands Cheatsheet

Helm is the reference package manager for Kubernetes. This cheatsheet gathers the essential Helm charts Kubernetes commands for installing, updating, debugging, and managing your releases in production. According to Orca Security 2025, 70% of organizations use Helm to deploy on Kubernetes.

TL;DR: Helm simplifies Kubernetes deployments via reusable charts. Master helm install, helm upgrade, helm rollback, and helm template to manage your releases effectively.

These skills are at the heart of the LFD459 Kubernetes for Application Developers training.

What is Helm and Why Use It?

Helm is a templating and packaging tool for Kubernetes that encapsulates YAML manifests in versioned charts. A chart is a collection of files describing a Kubernetes application. A release is a deployed instance of a chart.

Concept	Definition
Chart	Helm package containing templates, values, and metadata
Release	Instance of a chart deployed in a cluster
Repository	Server hosting Helm charts
Values	YAML file for custom configuration

Remember: Helm v3 removed Tiller. All operations run client-side with kubeconfig RBAC permissions.

How to Install and Configure Helm?

Quick Installation

# macOS
brew install helm

# Linux (official script)
curl https://raw.githubusercontent.com/helm/helm/main/scripts/get-helm-3 | bash

# Verify installation
helm version
# version.BuildInfo{Version:"v3.14.0", ...}

Repository Configuration

# Add a repository
helm repo add bitnami https://charts.bitnami.com/bitnami
helm repo add stable https://charts.helm.sh/stable

# Update indexes
helm repo update

# List configured repos
helm repo list
# NAME      URL
# bitnami   https://charts.bitnami.com/bitnami

# Search for a chart
helm search repo nginx
helm search hub prometheus  # Search on Artifact Hub

To understand Kubernetes fundamentals before using Helm, consult the Kubernetes system administrator guide.

What Are the Essential Helm Installation Commands?

Command	Description	Example
`helm install`	Install a chart	`helm install myapp bitnami/nginx`
`helm install -f values.yaml`	Install with custom values	`helm install myapp ./chart -f prod.yaml`
`helm install --set`	Inline override	`helm install myapp bitnami/nginx --set replicaCount=3`
`helm install --dry-run`	Simulate without deploying	`helm install myapp ./chart --dry-run`
`helm install --debug`	Verbose mode	`helm install myapp ./chart --debug`

Installation Examples

# Basic installation
helm install redis bitnami/redis -n cache --create-namespace

# Installation with values file
helm install api ./api-chart -f values-prod.yaml -n production

# Installation with multiple overrides
helm install web bitnami/nginx \
--set service.type=LoadBalancer \
--set replicaCount=3 \
--set resources.limits.memory=512Mi

# Generate name automatically
helm install bitnami/postgresql --generate-name

Remember: Use --dry-run --debug systematically before any deployment to validate generated manifests.

Managing ConfigMaps and Secrets Kubernetes integrates directly into your Helm charts via templates.

How to Manage Helm Releases and Updates?

Release Management Commands

Command	Description	Example
`helm list`	List releases	`helm list -A` (all namespaces)
`helm status`	Release status	`helm status myapp -n prod`
`helm upgrade`	Update a release	`helm upgrade myapp ./chart`
`helm rollback`	Rollback to a revision	`helm rollback myapp 2`
`helm uninstall`	Delete a release	`helm uninstall myapp -n prod`

Update Workflow

# List active releases
helm list -n production
# NAME    NAMESPACE   REVISION  STATUS    CHART         APP VERSION
# api     production  5         deployed  api-1.2.0     2.0.0

# Update with new values
helm upgrade api ./api-chart -f values-prod.yaml -n production

# View revision history
helm history api -n production
# REVISION  STATUS      DESCRIPTION
# 4         superseded  Upgrade complete
# 5         deployed    Upgrade complete

# Rollback if there's a problem
helm rollback api 4 -n production

To diagnose post-deployment errors, refer to the guide Resolve common Kubernetes deployment errors.

How to Debug Helm Templates and Deployments?

Debugging Commands

# View generated manifests without deploying
helm template myapp ./chart -f values.yaml

# Validate chart syntax
helm lint ./chart

# Test rendering with debug
helm install myapp ./chart --dry-run --debug 2>&1 | head -100

# View post-install notes
helm get notes myapp -n production

# Get effective values
helm get values myapp -n production --all

# Get deployed manifests
helm get manifest myapp -n production

Debugging Common Errors

# Template error?
helm template ./chart 2>&1 | grep -i error

# Chart not found?
helm repo update && helm search repo <name>

# Resource conflict?
helm get manifest myapp | kubectl apply --dry-run=server -f -

Remember: helm get manifest + kubectl diff lets you compare desired state vs current cluster state.

Kubernetes Application Development covers these debugging techniques in depth for Full-Stack Kubernetes developers.

What Are the Chart Creation Commands?

Chart Structure

# Create a new chart
helm create mychart
# mychart/
# ├── Chart.yaml          # Metadata
# ├── values.yaml         # Default values
# ├── charts/             # Dependencies
# └── templates/          # Kubernetes manifests
#     ├── deployment.yaml
#     ├── service.yaml
#     ├── _helpers.tpl    # Reusable functions
#     └── NOTES.txt       # Post-install message

Packaging Commands

Command	Description	Example
`helm create`	Generate a chart skeleton	`helm create api-chart`
`helm package`	Create a .tgz archive	`helm package ./mychart`
`helm dependency update`	Download dependencies	`helm dep update ./chart`
`helm show values`	Display default values	`helm show values bitnami/nginx`

# Package for distribution
helm package ./mychart --version 1.2.0 --app-version 2.0.0
# mychart-1.2.0.tgz

# Inspect a remote chart
helm show chart bitnami/redis
helm show readme bitnami/redis

The LFD459 training teaches Helm template creation for Kubernetes deployment in production.

What Are Common Pitfalls with Helm?

Pitfall	Symptom	Solution
Orphan release	`helm list` empty but resources present	Manual `kubectl delete` then `helm install`
Stuck hooks	Release in `pending-upgrade`	`kubectl delete job`
Values not applied	Config unchanged after upgrade	Check `--reuse-values` vs `-f values.yaml`
Missing namespace	Installation error	Add `--create-namespace`
Insufficient RBAC	Forbidden errors	Check Helm ServiceAccount

Anti-Patterns to Avoid

# ❌ Never use --force without understanding
helm upgrade --force  # Deletes and recreates resources

# ✅ Prefer --atomic for automatic rollback
helm upgrade myapp ./chart --atomic --timeout 5m

# ❌ Avoid --reuse-values with structure changes
helm upgrade myapp ./chart --reuse-values

# ✅ Always explicitly specify values
helm upgrade myapp ./chart -f values-prod.yaml

Remember: Use --atomic in CI/CD to guarantee automatic rollback on deployment failure.

To learn more about managing Helm Kubernetes releases in multi-cluster environments, explore the Kubernetes Security section.

Helm Commands Summary Table

Category	Command	Usage
Repos	`helm repo add/update/list`	Manage chart sources
Install	`helm install -f values.yaml`	Deploy with configuration
Upgrade	`helm upgrade --atomic`	Safe update
Rollback	`helm rollback`	Restore a version
Debug	`helm template --debug`	Validate manifests
Info	`helm get values/manifest/notes`	Inspect a release
Package	`helm package/lint`	Create and validate charts

According to the CNCF Annual Survey 2025, 82% of container users run Kubernetes in production. Mastering Helm is therefore essential.

Consult the Kubernetes Training: Complete Guide for an overview of available training paths, including sessions in Strasbourg, Toulouse, Luxembourg, and Brussels.

Take Action: Helm and Kubernetes Training

Develop your Helm and Kubernetes skills with SFEIR Institute:

LFD459 Kubernetes for Application Developers: 3 days to master deployments, Helm charts, and CKAD preparation
LFS458 Kubernetes Administration: 4 days of intensive training for CKA certification
Kubernetes Fundamentals: 1 day to discover key concepts

Contact our advisors to build your Backend Kubernetes developer training path suited to your level.

Key Takeaways