Helm

Helm is the package manager for Kubernetes, providing a standard way to define, install, version, and manage Kubernetes applications. Often described as the apt or yum of Kubernetes, Helm simplifies the complexity of deploying multi-resource Kubernetes applications by packaging all necessary manifests into a single unit called a chart.

A Helm chart is a collection of YAML templates and default configuration values that define a complete Kubernetes application. Charts can contain deployments, services, config maps, secrets, ingresses, persistent volume claims, RBAC configurations, and any other Kubernetes resources needed to run an application. Charts are parameterized using Go templates and a values file, allowing the same chart to be deployed multiple times with different configurations for different environments, clusters, or use cases.

The values system in Helm is one of its most powerful features. Each chart defines a set of default values in a values.yaml file that controls the behavior of the templates. When installing or upgrading a chart, users can provide custom values through a values file or individual --set flags to override defaults. This makes it practical to use the same chart for a lightweight development deployment and a production deployment with high availability, resource quotas, and custom ingress configuration.

Helm repositories are package registries where charts are stored and distributed. The Helm Hub (now Artifact Hub) aggregates charts from hundreds of public repositories, making it easy to find ready-made charts for popular applications including Nginx, PostgreSQL, Redis, Prometheus, Grafana, Elasticsearch, Kafka, and countless others. Organizations can also host private chart repositories for proprietary applications and configurations.

Release management is a core capability of Helm. When a chart is installed in a Kubernetes cluster, Helm tracks it as a named release with a revision history. Subsequent upgrades create new revisions, and the helm rollback command can revert to any previous revision instantly. This makes Helm deployments auditable and recoverable, providing a safety net for production deployments.

Helm hooks allow chart authors to define lifecycle hooks that execute Kubernetes jobs at specific points during the release lifecycle such as pre-install, post-install, pre-upgrade, post-upgrade, pre-rollback, and pre-delete. Hooks are commonly used for database migrations, configuration validation, backup operations, and cleanup tasks that must run in coordination with application deployments.

Chart testing and validation are supported through the ct (chart testing) tool, which provides automated linting and testing for charts in CI pipelines. The helm lint command checks charts for potential issues before deployment, and helm template renders the chart templates for manual inspection or automated diffing.

The Helm plugin system allows extending the Helm CLI with additional functionality such as secrets management, drift detection, automated chart updates, and environment-specific configuration management. Popular plugins include helm-secrets for managing encrypted secrets, helm-diff for previewing changes before applying them, and helm-unittest for unit testing chart templates.

Helm is a graduated project of the Cloud Native Computing Foundation (CNCF) and is the de facto standard for application package management in the Kubernetes ecosystem, with widespread adoption across enterprises, cloud providers, and the open source community.