Helm (package manager)

Helm (package manager)
Name	Helm
Author	Cloud Native Computing Foundation
Developer	CNCF, Google, Deis, Microsoft, Red Hat
Released	2015
Programming language	Go
Operating system	Linux, macOS, Windows
Platform	Kubernetes
Genre	Package manager
License	Apache License 2.0

Helm (package manager) is an open-source package manager designed for Kubernetes, providing templated deployment and lifecycle management of cloud-native applications. It was originally developed by engineers from Google, Deis, and collaborators and later adopted by the Cloud Native Computing Foundation, becoming central to deployment workflows used by organizations such as Microsoft, Red Hat, Amazon Web Services, and IBM. Helm integrates with ecosystems including Docker, Prometheus, Istio, Envoy (software), and Flux (software) to standardize application packaging and distribution.

History

Helm originated in 2015 as a project by contributors associated with Deis and Google to address repeatable application deployment patterns on Kubernetes. Early development paralleled the rise of Docker container orchestration and coincided with the formation of the Cloud Native Computing Foundation which later accepted Helm as a hosted project. Major milestones include the transition from a server-side component to a client-only architecture influenced by security discussions involving CoreOS, the deprecation of the original server component following debates around multi-tenant models similar to issues discussed in Kubernetes community meetings, and widespread adoption across commercial platforms such as Amazon Web Services, Google Cloud Platform, and Microsoft Azure.

Architecture and components

Helm's architecture centers on a client binary written in Go (programming language) and a packaging format that encapsulates Kubernetes resources. Components include the helm client, templating engine, chart archive, and repositories compatible with HTTP hosting and object stores used by companies like GitHub, Google Cloud Storage, Amazon S3, and Azure Blob Storage. Integrations with projects such as Kustomize, Flux CD, Argo CD, Prometheus, and OpenShift illustrate Helm’s role in continuous delivery, monitoring, and platform operations. Security-related components interact with Role-Based Access Control, TLS, and standards promoted by the CNCF ecosystem.

Chart format and chart repository

Helm packages, known as charts, are distributed as compressed archives that include templated manifests, default values, and metadata. The chart format was influenced by packaging conventions used by projects like Debian, RPM Package Manager, and archival standards used by GNU Tar. Charts often reference images hosted on registries maintained by Docker Hub, Quay.io, Google Container Registry, and Amazon ECR. Chart repositories can be served from static web hosts such as GitHub Pages or artifact registries provided by enterprises including JFrog Artifactory and Harbor (software), enabling ecosystems of public repositories like those maintained by Bitnami and community collections showcased on platforms curated by the CNCF.

Installation and release management

Helm streamlines installation and release workflows by creating, upgrading, rolling back, and uninstalling named releases in Kubernetes clusters. Release management practices leverage patterns popularized in Continuous integration and Continuous delivery pipelines used by projects such as Jenkins, Travis CI, CircleCI, and GitLab CI/CD. Operators use Helm alongside infrastructure automation tools like Terraform, Ansible, and Puppet to manage composable stacks across cloud providers including Amazon Web Services, Google Cloud Platform, and Microsoft Azure. Advanced release strategies integrate traffic control tools from Istio, Linkerd, and Envoy (software) for canary and blue–green deployments.

Usage and commands

Common Helm commands provide lifecycle control: creating charts, templating manifests, installing releases, upgrading, and rollback. Workflows mirror commands found in traditional package managers and are executed on developer workstations or CI runners such as GitHub Actions, GitLab Runner, Bamboo (software), or Jenkins. Helm templates can be combined with tools like Kustomize or versioned in repositories backed by Git (software), enabling GitOps patterns used by Argo CD and Flux (software). Administrators connect Helm to cluster APIs managed via kubectl and monitor releases with logging and metrics systems from ELK Stack, Prometheus, and Grafana.

Security and governance

Security considerations for Helm have driven architectural changes, governance by the Cloud Native Computing Foundation, and policy integrations with tools such as OPA (software), Gatekeeper (software), and Trivy. The project follows CNCF governance models similar to other hosted projects like Kubernetes and etcd (software), with community-submitted charts subject to review practices used by repositories maintained by Bitnami and enterprise vendors like Red Hat. Vulnerability scanning, provenance, and signing of charts are implemented with standards influenced by The Update Framework and OpenPGP-like practices adopted by registries across the CNCF landscape.

Category:Cloud Native Computing Foundation projects Category:Kubernetes