Helmfile
Declarative spec and CLI for deploying Helm charts, Kustomize configs and Kubernetes manifests as Helm releases.
Tested on LinuxKnown vulnerabilities
Use it
Before you install: known vulnerabilities
pickfit found 1 known high or critical vulnerability in the packages a fresh install brings (OSV.dev, 16 Nov 2026). Weigh this before you install it.
go:github.com/klauspost/compress v1.19.1Panic on two-block frames in github.com/klauspost/compress (GO-2026-6865, high, fixed in 1.20.2)
Linux x86_64
You need first
- System packages:
helm,helm-diff
Download helmfile v1.8.4 and helm v4.3.2 release binaries into ~/.local/bin
set -e; cd /tmp && curl -fsSLO https://github.com/helmfile/helmfile/releases/download/v1.8.4/helmfile_1.8.4_linux_amd64.tar.gz && tar xzf helmfile_1.8.4_linux_amd64.tar.gz helmfile && install -m755 helmfile ~/.local/bin/helmfile && curl -fsSLO https://get.helm.sh/helm-v4.3.2-linux-amd64.tar.gz && tar xzf helm-v4.3.2-linux-amd64.tar.gz && install -m755 linux-amd64/helm ~/.local/bin/helmInstall kustomize v5.8.3 release binary (needed for patches)
set -e; cd /tmp && curl -fsSLO https://github.com/kubernetes-sigs/kustomize/releases/download/kustomize%2Fv5.8.3/kustomize_v5.8.3_linux_amd64.tar.gz && tar xzf kustomize_v5.8.3_linux_amd64.tar.gz && install -m755 kustomize ~/.local/bin/kustomize
Where the README and reality differ
- README: Prerequisites: helm and helm-diff
What worked: strategicMergePatches/jsonPatches (and kustomizations) also need the kustomize binary on PATH; without it helmfile fails with 'exec: "kustomize": executable file not found in $PATH'
Check that it works
helmfile --versionThe output should contain “helmfile version 1.8.4”.
First thing to try
cd /tmp && rm -rf my-project && helmfile create my-project && cd my-project && find . -type fRun helmfile create <project> to start a new project with a helmfile.yaml.
What it does
- Declare the Helm releases you want and apply themTested
How to use it
- Write a helmfile.yaml listing each release with its name, namespace, chart and values.
- Run
helmfile template -f helmfile.yamlto render the manifests for those releases.
- Reuse infrastructure modules from Git or S3Tested
How to use it
- In your helmfile, add a
helmfiles:entry with apathsuch asgit::<repo-url>@helmfile.yaml?ref=<branch>. - Run
helmfile template -f <file>to render the releases from that module.
- In your helmfile, add a
- Deploy kustomizations and manifests as Helm releasesTested
How to use it
- Add a release whose
chartpoints to a directory of plain Kubernetes manifests. - Run
helmfile template -f <file>to render them as a Helm release.
- Add a release whose
- Patch Kubernetes resources without forking chartsTested
How to use it
- Add a
strategicMergePatcheslist to a release, naming the resource and the fields to change. - Run
helmfile template -f <file>to see the chart output with the patch applied.
- Add a
How far pickfit got
Linux x86_64
- Installs
- Starts
- 4 of 4 features work
- Works offline
macOS and Windows: the project says it runs there; pickfit hasn’t tried it.
Good for
- keep chart value files in version control
- apply CI/CD to Kubernetes configuration changes
- periodically sync clusters to avoid environment skew
- generate all-in-one manifests for ArgoCD
How pickfit tested it
Each run starts from a clean machine and follows the steps above. How pickfit verifies
Linux x86_64
Its main function works
- Replayed from scratch
- Works offline
- Checked on 15 Nov 2026
- Version 1.8.4
Differences the test machine hit
- README: Install candidates: go install / pacman / zypper / mise
In the test: Used README option 1 (binary download from GitHub releases): no Go toolchain, no pacman/zypper on Debian, mise is not installed - README: helmfile apply syncs your cluster
In the test: No Kubernetes cluster here; checked the features with 'helmfile template' instead. helm-diff and 'helmfile init' were not needed for template - README: helm (any version)
In the test: helmfile 1.8.4 templated charts with helm v4.3.2 without problems