sincecutoff.com
← all changes

helmfile kubedog startup-only pod logs

Introduced 2026-10-16 · score 0.98

HOW TO USE IT

When 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-ready

WHY THIS HELPS

When reviewing deployment logs for a kubedog-tracked release, limit routine pod output to startup while tracking readiness and failures for every pod.

BEFORE THIS CHANGE

With `trackLogs: true`, use the default full streaming behavior, which continues printing logs throughout tracking.

REQUIREMENTS AND LIMITATIONS

  • Version: v1.8.2
  • track-mode / trackMode (required): Set to `kubedog` to enable kubedog tracking.
  • track-logs / trackLogs (required): Enable log output from tracked resources; required for `track-logs-until-ready` to apply.
  • track-logs-until-ready / trackLogsUntilReady (required): Stop routine pod logs after each pod first becomes ready; config default is `false`.
  • track-timeout / trackTimeout: Tracking timeout in seconds; default is 300. The example uses 600.
  • Prerequisite: Enable kubedog tracking with `trackMode: kubedog` or `--track-mode kubedog`, and enable routine logs with `trackLogs: true` or `--track-logs`.
  • The option applies only when `trackLogs` is enabled; `trackFailedLogs: true` alone retains failed-only behavior.
  • Job logs retain their existing behavior.
  • Kubernetes readiness timestamps have second precision, so logs from the readiness second are retained.
  • Log output remains limited to startup if the same pod later becomes unready or fails; replacement pods reset the filter.
  • Kubernetes continues collecting logs; the change limits printed output.

FIRST-PARTY EVIDENCE

Check the installed version and the source before using it. Entry JSON

Report a problem with this card