Sefism is free for learners. We are here to help you grow, one step at a time.Join for free
Sefism.
Guide · OtherFree

Helm Documentation

The official docs for Helm, the package manager for Kubernetes and a CNCF graduated project. Learn to install, upgrade and roll back charts, then write your own with the chart template guide and best practices. Now covering Helm 4, with Helm 3 docs still a click away.

Current version

Helm 4.3.0

helm.sh · Sept 2026

GitHub stars

30.3k (helm/helm)

GitHub · Sept 2026

CNCF maturity

Graduated

helm.sh · Sept 2026

Format

Guide

Topic

Other

Provider

Helm (CNCF)

Time needed

A few evenings for the basics, a week to write good charts

Level

Intermediate

Access

Free

What Helm is

Helm is the package manager for Kubernetes. A Helm chart bundles the templates for everything an application needs in a cluster (Deployments, Services, ConfigMaps and the rest) together with a values.yaml file of settings. Installing a chart creates a release you can upgrade, inspect and roll back as one unit. Helm is a Cloud Native Computing Foundation graduated project. Helm 4 was released in November 2025, and in September 2026 the docs default to Helm 4.3.0, with a switcher for Helm 3 and the long retired Helm 2.

What the docs cover

  • Introduction and how-to guides: installing Helm, the quickstart, and everyday tasks with repositories and releases.
  • Topics: charts, chart repositories, registries, hooks, provenance and signing, and the Helm 4 overview explaining what changed from Helm 3.
  • Best practices: naming, values, templates, labels, dependencies and RBAC conventions for charts others will use.
  • Chart template guide: a step by step tutorial on Go templates, built in objects, functions, flow control, named templates and debugging.
  • Plugins, Helm commands and the Go SDK: the full CLI reference and how to embed Helm in your own tools.

Is it worth learning?

Yes, if you touch Kubernetes. Most third party software you install in a cluster ships as a Helm chart, GitOps tools such as Argo CD deploy charts directly, and many companies package their own services the same way. Even teams that prefer Kustomize end up reading and debugging charts.

Prerequisites and time

You need a Kubernetes cluster and kubectl, plus a working understanding of the objects a chart creates. YAML indentation will matter more than you expect. Installing, upgrading and rolling back a public chart takes an evening. Working through the chart template guide and the best practices section to write a chart for your own service takes about a week of evenings.

Free or paid?

Helm and its documentation are free and open source.

Common questions

Helm 3 or Helm 4? Learn on the version your team runs, and check the version selector at the top of the docs so examples match. If you are starting fresh, the current docs cover Helm 4, and the Helm 4 overview lists what changed.

Helm or Kustomize? They solve overlapping problems differently: Helm templates and packages, Kustomize patches plain YAML. Many teams use both, and Argo CD supports both.

What can I do after it? Install and manage third party charts with confidence, write a chart for your own service with sensible values, debug a failing template with helm template, and roll back a bad release.

Best for: DevOps, platform and backend engineers deploying to Kubernetes.

devopskubernetesopen sourcecloud

Ready to start?

Opens on Helm (CNCF) in a new tab.

Open resource
Link broken or out of date?

Report a problem

With "Helm Documentation". Only Tauseef reads this.

Work with me

Stuck on something specific?

Writing only gets you so far. If you want an answer to your situation rather than the general case, book a session and we will work through it together. Sessions are free for approved Sefism members, and a few slots open each week.