Hysen Labshelm
The Kubernetes Package Manager
Helm: the package manager Kubernetes adopted
Helm bundles Kubernetes resources into Charts, which makes installing and updating applications on a cluster feel closer to apt or homebrew than to writing manifests by hand.
Charts as packages
Helm is a tool for managing Charts, which the README defines as packages of pre configured Kubernetes resources. The mental model maps straight onto package managers from other worlds. Users can find and use popular software packaged as Helm Charts, share their own applications as Charts, create reproducible builds, manage Kubernetes manifest files, and manage releases of Helm packages. Everything hangs off that single concept.
Where Helm fits
The README compares Helm to apt, yum, or homebrew, but for Kubernetes. It renders templates and communicates with the Kubernetes API, and it runs on a laptop, in CI or CD, or wherever the user wants. Charts can be stored on disk or fetched from remote chart repositories. The point of the comparison is to set expectations: this is the install path for clusters, the way a package manager is the install path for an operating system.
What a Chart contains
A Chart has a minimal shape. It contains at least a description of the package in a Chart.yaml file, plus one or more templates holding Kubernetes manifest files. Templates are what make Charts useful, since they let a single package render slightly different resources depending on the values you pass. Everything else is convention layered on top of that core.
The two versions in support
Version status is spelled out for anyone coming from an older setup. Helm v4 is the current stable release, developed on the main branch. Helm v3 is in support mode on a version branch, with bug fixes until July 2026 and security fixes until November 2026. Knowing which branch to track, and for how long, is exactly the kind of detail a team planning an upgrade needs before it starts.
Community notes