helm を Homebrew でインストール

プロジェクトリンク

• ホームページ
• リポジトリ

コマンドとエイリアス

• helm

プロジェクトの歴史

The Helm project traces its first version to November 2015 at the first KubeCon. The Helm team describes Helm 1, also known as Helm Classic, as modeled on Homebrew and aimed at helping individual developers package Kubernetes resources and deploy them into clusters.

In January 2016, Deis' Helm team joined forces with Google, Skippbox, and Bitnami to build a new version focused on teams and a growing Kubernetes user community. That work led to the Helm 2 architecture and the chart ecosystem that many Kubernetes users adopted.

Helm joined the Cloud Native Computing Foundation in June 2018. Helm 3 reached its first stable release in November 2019, removing Tiller, refactoring the Go SDK for broader use, and changing internals while preserving the chart-centered workflow for users familiar with Helm 2.

採用の歴史

Helm adoption tracked the growth of Kubernetes itself. Its docs describe chart repositories, `helm search`, `helm install`, `helm upgrade`, `helm rollback`, `helm get`, and `helm uninstall` as ordinary package operations for cluster workloads.

The Helm 3 release post describes a large contributor base and thousands of community members maintaining charts through Helm Hub-era infrastructure. The chart discovery story later centered on Artifact Hub, which the Helm docs use for `helm search hub`.

Package-manager adoption for the CLI is broad: the supplied metadata lists Homebrew, Alpine, Fedora, MacPorts, Nix, Arch, Scoop, winget, and openSUSE packaging for the Kubernetes-oriented Helm CLI.

使われ方

Users add chart repositories, search for charts, install a chart as a named release, pass values with YAML files or `--set`, upgrade releases, inspect status and values, roll back revisions, and uninstall releases.

Helm charts package Kubernetes resource definitions alongside metadata and default values. A chart can be installed many times into a cluster, producing separate releases with their own names and histories.

Helm's local repository configuration is stored in `repositories.yaml` under the user's Helm config directory. Because repository entries can include credentials, that file is also treated as a credentials location in the curation data.

パッケージ好きにとっての重要性

Helm is one of the clearest examples of package-manager culture crossing into infrastructure. It has packages, repositories, dependency declarations, install and upgrade verbs, versioned releases, rollback history, and a registry/discovery ecosystem, but the installed artifacts are Kubernetes resources rather than files under `/usr`.

The Helm 2 to Helm 3 transition is also package-history material: removing Tiller reduced cluster-side moving parts and aligned Helm more closely with Kubernetes RBAC and client-side release management expectations.

For maintainers, Helm created a new packaging discipline around chart metadata, values schema, generated documentation, provenance, OCI distribution, and chart repository layout.

タイムライン

• 2015: Helm 1 released at the first KubeCon.
• 2016: Deis, Google, Skippbox, and Bitnami collaborate on the next Helm generation.
• 2018: Helm joins the Cloud Native Computing Foundation.
• 2019: Helm 3.0.0 stable release published.
• 2020: Helm celebrates CNCF graduation.
• 2020s: Helm chart discovery and search workflows use Artifact Hub in official documentation.

Related projects

• Kubernetes is the deployment platform Helm packages target.
• Homebrew inspired Helm Classic's package-manager model.
• Deis, Google, Skippbox, and Bitnami are named in the Helm 3 history as early collaborators.
• Artifact Hub is the chart discovery service used by `helm search hub`.
• helm-docs and helm-ls are neighboring tools for chart documentation and editor assistance.

ソース

• https://api.github.com/repos/helm/helm
• https://github.com/helm/helm
• https://helm.sh/blog/celebrating-helms-cncf-graduation/
• https://helm.sh/blog/helm-3-released/
• https://helm.sh/docs
• https://helm.sh/docs/intro/using_helm/
• https://helm.sh/docs/topics/charts/