We scan this tool’s changelog a few times a day and keep the changes that would alter your agent’s next action: 19 since February 2026, each linked to its source.
helmfileWhen syncing a service in nested Helmfiles, run `helmfile -l dir=<path> sync` to select releases whose defining Helmfile is in that directory or a subdirectory; Helmfile skips sub-Helmfile branches whose location rules out a match.
helmfile -l dir=apps/<single-service> syncWhen tracking a release with kubedog and routine logs enabled, set `trackLogsUntilReady: true` or pass the documented flags to `helmfile apply`. Each pod’s routine logs stop after its first Ready transition while readiness and failure tracking continue.
helmfile apply --track-mode kubedog --track-timeout 600 --track-logs --track-logs-until-readyWhen using Kubedog tracking with `trackLogs` or `trackFailedLogs` on `helmfile apply` or `helmfile sync`, set `trackLogsInterval` on the release to control log update frequency. An explicitly supplied `--track-logs-interval` overrides it; otherwise it overrides the `10s` default (minimum `1s`).
releases:
- name: <release>
chart: <chart>
trackMode: kubedog
trackLogs: true
trackLogsInterval: 1sWhen syncing releases, set `continueOnError: true` on releases whose failures should not stop independent DAG branches. Helmfile skips dependent releases and exits non-zero if any release fails.
releases:
- name: app-a
chart: ./charts/app-a
continueOnError: true
- name: app-b
chart: ./charts/app-b
continueOnError: true
helmfile syncWhen chart preparation fails for a release, run Helmfile with `--allow-failed-releases` to skip that release, continue preparing other releases, and report failures at the end.
helmfile --allow-failed-releases templateWhen Helmfile hook shell commands must be disabled, set `HELMFILE_DISABLE_HOOKS=true` for the Helmfile invocation. If hooks are configured while this setting is active, Helmfile returns an error instead of triggering them.
HELMFILE_DISABLE_HOOKS=true helmfile <command>When a release needs a dynamic enablement condition, set `conditionTemplate` to a Go template that renders a boolean. If both condition fields are set, its rendered value replaces `condition`; `list` does not evaluate it.
releases:
- name: <release-name>
chart: <repository/chart>
conditionTemplate: '{{`{{ eq .Release.Namespace "kube-system" }}`}}'When a chart uses `lookup()` and rendering needs live cluster values, pass `--template-args="--dry-run=server"` to `helmfile template`, `apply`, or `sync`. `--template-args` forwards extra arguments to Helm rendering.
helmfile template --template-args="--dry-run=server"When applying a Helmfile release with live kubedog progress, run `helmfile apply --track-mode kubedog`. Helmfile tracks resources in parallel with Helm and buffers Helm output per release. [Release notes](https://github.com/helmfile/helmfile/releases/tag/v1.6.0)
helmfile apply --track-mode kubedogBefore applying planned changes, run `helmfile doctor` to review the diff; use `--output json` for a structured report. High-risk findings exit 2 unless `--force` is passed.
export HELMFILE_LLM_API_KEY="<api-key>"
export HELMFILE_LLM_MODEL="<model-id>"
helmfile doctor --output json