GitOps and Kubernetes delivery
What is Helm? An introduction to Helm Project's package manager for Kubernetes
Helm is the package manager for Kubernetes. It is a way to find, share, and use software built for Kubernetes, packaged as Helm Charts. Charts define, install, and upgrade even complex Kubernetes applications.
- Tool
- Helm
- Made by
- Helm Project
- Official site
- helm.sh
- Category
- GitOps and Kubernetes delivery
Who makes Helm
Helm is developed by the Helm Project and maintained by the Helm community. It is a graduated CNCF project.
The official website is linked below.
Official website: helm.sh
What Helm is for
Helm packages Kubernetes software so it can be found, shared, and used. The unit of packaging is the Helm Chart, which defines an application, installs it, and upgrades it, including applications that are complex.
Charts are easy to create, version, share, and publish. A chart can be hosted on a public or private server, so a team can distribute its own software internally or publish it more widely.
Who Helm is for
The vendor names three groups: Kubernetes users, chart authors and maintainers, and contributors to the Helm project.
Kubernetes users install and upgrade software from charts. Chart authors and maintainers create, version, and publish those charts. Contributors work on Helm itself.
Notable capabilities
Helm covers the lifecycle of a packaged Kubernetes application, from discovery and installation through upgrades and rollback. Helm 4 adds a set of changes to plugins, chart sourcing, status reporting, and values handling.
- In-place upgrades and custom hooks for updates.
- Rollback of a release to an older version.
- Chart hosting on public or private servers, with Artifact Hub for exploring charts from public repositories.
- Installation through a package manager or by downloading a binary, with binary releases for a variety of operating systems.
- Cryptographic signatures on releases that confirm the binary was built and signed by maintainers.
- Helm 4 optional WebAssembly-based plugin runtime, launching with CLI, getter, and post-renderer plugin types.
- Helm 4 installation of charts by OCI digest; charts with a non-matching digest are not installed.
- Helm 4 kstatus integration for detailed deployment status, server-side apply as the default for new chart releases, and values split across multiple YAML files.
How Helm fits GitOps and Kubernetes delivery
In GitOps and Kubernetes delivery, Helm supplies the packaging format. A chart describes what to deploy, and the release mechanics of install, upgrade, and rollback act on that package.
Within the wider niche of CI/CD and deployment platforms, Helm is a deployment-time component rather than a full pipeline. Other delivery tools can consume Helm charts as their deployment unit.
Frequently asked questions
What is Helm used for?
Helm is used to find, share, and use software built for Kubernetes. Helm Charts define, install, and upgrade Kubernetes applications, including complex ones.
Who develops Helm?
Helm is developed by the Helm Project and maintained by the Helm community. It is a graduated CNCF project.
Can Helm roll back a release?
Yes. Helm can roll a release back to an older version. It also supports in-place upgrades and custom hooks for updates.
Where can I find Helm charts?
Artifact Hub lets users explore Helm charts from public repositories. Charts can also be hosted on public or private servers.
What is new in Helm 4?
Helm 4 adds an optional WebAssembly-based plugin runtime, installation by OCI digest, kstatus integration, server-side apply by default for new chart releases, and values split across multiple YAML files.
Deployelm is independent and is not affiliated with Helm Project. Product names belong to their owners. Features change; confirm details on the official website.