Helm (software)

Helm (software)
Name	Helm
Title	Helm
Developer	Cloud Native Computing Foundation
Released	2015
Latest release	3.x
Repository	https://github.com/helm/helm
Programming language	Go
License	Apache License 2.0

Helm (software) Helm is an open-source package manager for Kubernetes that streamlines deployment, configuration, and lifecycle management of containerized applications. It provides templating, release management, and a repository model that integrates with container registries and continuous delivery systems used by organizations such as Google, Amazon Web Services, Microsoft, Red Hat, and VMware. Helm is maintained under governance by the Cloud Native Computing Foundation and commonly used alongside tools like Docker, Prometheus, Grafana, and Istio.

Overview

Helm organizes application resources into reusable packages called charts that bundle YAML manifests, templates, and metadata for distribution via chart repositories. Charts enable reproducible deployments across environments managed by Kubernetes clusters, including distributions such as OpenShift, GKE, EKS, and AKS. The project addresses common operational patterns found in continuous delivery pipelines implemented with Jenkins, GitLab CI/CD, Argo CD, and Flux. Helm's functionality overlaps with configuration management systems used by enterprises like Red Hat and cloud-native ecosystems sponsored by the Linux Foundation.

History and development

Helm originated in 2015 within the Deis team and gained adoption as a declarative package manager during early growth of the Kubernetes ecosystem. Key milestones include the transition of maintainership to the Cloud Native Computing Foundation and the major version changes that separated server-side components from client-side tooling. Notable contributors and organizations involved in development include engineers from Google, IBM, Microsoft, Red Hat, and startups such as Heptio and CoreOS. The project evolved through proposals and design documents influenced by practices from Homebrew, apt, and RPM Package Manager, adapting package distribution for cloud-native workloads.

Architecture and concepts

Helm's core concepts include charts, releases, templates, values, and repositories. A chart encapsulates one or more Kubernetes manifests templated with the Go templating engine and parameterized by values files; this design mirrors packaging ideas from Debian and Red Hat Enterprise Linux. Releases represent deployed instances of charts tracked by Helm's client and storage backend; storage backends may integrate with cluster-native storage such as etcd and orchestration layers like Kubelet. Chart repositories host index files and packaged charts; registries used include Docker Hub, OCI-compliant registries endorsed by Cloud Native Computing Foundation members, and private artifact registries provided by JFrog and GitHub. Helm's architecture integrates with policy and admission systems such as Open Policy Agent and Gatekeeper for governance.

Usage and commands

Users interact with Helm through a command-line interface and APIs that perform chart lifecycle operations such as create, install, upgrade, rollback, and uninstall. Common commands mirror package manager verbs and integrate with CI/CD runners from projects like Jenkins X and Tekton; operators often script helm operations within pipelines that target clusters managed by Rancher or Kubernetes Operations (kOps). Release management workflows coordinate with observability stacks such as Prometheus and Grafana for monitoring, and incident response tooling from PagerDuty and Slack for alerts. Administrators rely on commands to template manifests for tools like Kustomize and to render manifests for security scanning by providers including Snyk and Aqua Security.

Ecosystem and plugins

An extensive ecosystem surrounds Helm, including official and community chart repositories, curated collections maintained by organizations like Bitnami, Artifact Hub, and cloud vendors. Plugin architectures permit extensions for repository management, chart linting, and interactions with container registries; notable plugins integrate with Harbor, Quay, Velero, and secrets backends such as HashiCorp Vault and AWS Secrets Manager. Third-party projects provide tooling for helm-based GitOps workflows, reconciliation controllers, and chart testing frameworks used by teams at Spotify, Salesforce, and Netflix.

Security and governance

Helm's security model includes chart signing, provenance verification, and best practices for templating to reduce injection risks; these controls complement admission controllers and image vulnerability scanners from vendors like Aqua Security, Snyk, and Anchore. Governance is provided by the Cloud Native Computing Foundation with a Technical Steering Committee and contributor guidelines modeled after other CNCF projects such as Prometheus and Envoy. Incident response and common CVE disclosures have driven improvements in the project's auditability and CI/CD scanning integrations, and security researchers from academic institutions and companies like Google and Microsoft contribute to threat modeling and mitigations.

Category:Kubernetes Category:Cloud Native Computing Foundation projects