Repository files navigation

Helm is a tool for managing Charts. Charts are packages of pre-configured Kubernetes resources.

Use Helm to:

• Find and usepopular software packaged as Helm Charts to run in Kubernetes
• Share your own applications as Helm Charts
• Create reproducible builds of your Kubernetes applications
• Intelligently manage your Kubernetes manifest files
• Manage releases of Helm packages

Helm is a tool that streamlines installing and managing Kubernetes applications.Think of it like apt/yum/homebrew for Kubernetes.

• Helm renders your templates and communicates with the Kubernetes API
• Helm runs on your laptop, CI/CD, or wherever you want it to run.
• Charts are Helm packages that contain at least two things:
  • A description of the package (Chart.yaml)
  • One or more templates, which contain Kubernetes manifest files
• Charts can be stored on disk, or fetched from remote chart repositories(like Debian or RedHat packages)

Helm v4 is currently under development on themain branch. This is unstable and the APIs within the Go SDK and at the command line are changing.Helm v3 (current stable) is maintained on thedev-v3 branch. APIs there follow semantic versioning.

Binary downloads of the Helm client can be found onthe Releases page.

Unpack thehelm binary and add it to your PATH and you are good to go!

If you want to use a package manager:

• Homebrew users can usebrew install helm.
• Chocolatey users can usechoco install kubernetes-helm.
• Winget users can usewinget install Helm.Helm.
• Scoop users can usescoop install helm.
• Snapcraft users can usesnap install helm --classic.
• Flox users can useflox install kubernetes-helm.

To rapidly get Helm up and running, start with theQuick Start Guide.

See theinstallation guide for more options,including installing pre-releases.

Get started with theQuick Start guide or plunge into thecomplete documentation

TheHelm roadmap uses GitHub milestones to track the progress of the project.

The development of Helm v4 is currently happening on themain branch while the development of Helm v3, the stable branch, is happening on thedev-v3 branch. Changes should be made to themain branch prior to being added to thedev-v3 branch so that all changes are carried along to Helm v4.

You can reach the Helm community and developers via the following channels:

• Kubernetes Slack:
  • #helm-users
  • #helm-dev
  • #charts
• Mailing List:
  • Helm Mailing List
• Developer Call: Thursdays at 9:30-10:00 Pacific (meeting details)

If you're interested in contributing, please refer to theContributing Guidebefore submitting a pull request.

Participation in the Helm community is governed by theCode of Conduct.