pickfit

BrowseInfra & DevOps tools

Helmfile

Declarative spec and CLI for deploying Helm charts, Kustomize configs and Kubernetes manifests as Helm releases.

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.1 Panic 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
  1. 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/helm
  2. Install 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 --version

The 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 f

Run helmfile create <project> to start a new project with a helmfile.yaml.

What it does

  • Declare the Helm releases you want and apply them
    How to use it
    1. Write a helmfile.yaml listing each release with its name, namespace, chart and values.
    2. Run helmfile template -f helmfile.yaml to render the manifests for those releases.
    Tested
  • Reuse infrastructure modules from Git or S3
    How to use it
    1. In your helmfile, add a helmfiles: entry with a path such as git::<repo-url>@helmfile.yaml?ref=<branch>.
    2. Run helmfile template -f <file> to render the releases from that module.
    Tested
  • Deploy kustomizations and manifests as Helm releases
    How to use it
    1. Add a release whose chart points to a directory of plain Kubernetes manifests.
    2. Run helmfile template -f <file> to render them as a Helm release.
    Tested
  • Patch Kubernetes resources without forking charts
    How to use it
    1. Add a strategicMergePatches list to a release, naming the resource and the fields to change.
    2. Run helmfile template -f <file> to see the chart output with the patch applied.
    Tested

How far pickfit got

Linux x86_64

  1. Installs
  2. Starts
  3. 4 of 4 features work
  4. 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

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.