No description
Find a file
Abdullah Kaya 2b128dcd27
docs: add LibreDB to ADOPTERS.md (#32704)
Signed-off-by: Abdullah Kaya <abdullah.kaya@libredb.org>
2026-09-30 09:28:44 -06:00
.github chore(deps): bump the github-actions group across 1 directory with 4 updates (#32701) 2026-09-29 07:09:30 -06:00
cmd/helm Updating the Go version 2026-08-25 20:42:36 -04:00
internal feat(storage): add internal/storage/driver for release v2 (#32667) 2026-09-21 06:38:27 -06:00
pkg feat(storage): add internal/storage/driver for release v2 (#32667) 2026-09-21 06:38:27 -06:00
scripts fix(scripts): clarify cache-busting behavior 2026-07-27 13:55:05 -05:00
testdata Do not explicitly set SNI in HTTPGetter 2025-03-23 14:34:02 -04:00
.gitignore chore: Add AI Vendor specific paths to .gitignore 2026-07-16 11:14:59 -07:00
.golangci.yml chore: Fix independent-merge lint issues 2026-08-31 13:35:39 -07:00
.goreleaser.yaml build: use goreleaser build with manual archive creation 2026-05-02 19:19:20 -06:00
ADOPTERS.md docs: add LibreDB to ADOPTERS.md (#32704) 2026-09-30 09:28:44 -06:00
AGENTS.md chore: Improve AGENTS.md 2026-02-23 16:55:25 -08:00
code-of-conduct.md Fixing the code of conduct pointer 2019-12-04 10:23:10 -05:00
CONTRIBUTING.md docs: improve CONTRIBUTING.md wording 2026-06-16 20:00:17 +05:30
go.mod chore(deps): bump github.com/ProtonMail/go-crypto from 1.5.0 to 1.5.2 (#32699) 2026-09-29 06:57:42 -06:00
go.sum chore(deps): bump github.com/ProtonMail/go-crypto from 1.5.0 to 1.5.2 (#32699) 2026-09-29 06:57:42 -06:00
KEYS chore: new KEYS entry for George Jenkins 2026-02-08 09:45:12 -08:00
LICENSE
Makefile fix(Makefile): update outdated .sha256 comment for Helm v4 (#32323) 2026-07-10 05:30:53 -06:00
OWNERS chore: move Evans Mungai from triage to maintainers 2026-01-01 13:28:01 +02:00
README.md docs: update version status for v4 stable release 2026-05-22 09:47:41 +02:00
SECURITY.md Adding security file 2020-01-28 10:58:27 -05:00

Helm

Build Status Go Report Card GoDoc CII Best Practices OpenSSF Scorecard LFX Health Score

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

Use Helm to:

  • Find and use popular 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 in a Handbasket

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 Development and Stable Versions

Helm v4 is the current stable release, developed on the main branch. Helm v3 is in support mode on the dev-v3 branch: bug fixes until July 8th 2026, security fixes until November 11th 2026.

Install

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

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

If you want to use a package manager:

  • Homebrew users can use brew install helm.
  • Chocolatey users can use choco install kubernetes-helm.
  • Winget users can use winget install Helm.Helm.
  • Scoop users can use scoop install helm.
  • Snapcraft users can use snap install helm --classic.
  • Flox users can use flox install kubernetes-helm.
  • Mise-en-place users can use mise use -g helm@latest

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

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

Docs

Get started with the Quick Start guide or plunge into the complete documentation.

Roadmap

The Helm roadmap uses GitHub milestones to track the progress of the project.

Helm v4 development happens on the main branch. Helm v3 is in support mode on the dev-v3 branch and receives only bug and security fixes.

Community, discussion, contribution, and support

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

Contribution

If you're interested in contributing, please refer to the Contributing Guide before submitting a pull request.

Code of conduct

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