chore: bump kubedog to stop leaking informers after tracking

Merged
DM
18d ago
+3-3

Summary

A long-lived process that runs a nelm release install with tracking on every reconcile (for example a controller embedding nelm v1) keeps shared informers alive after each tracking ends, each holding the cache of a resource type for a whole namespace, so memory grows until the process restarts. This bumps github.com/werf/kubedog from ad1e8a1 to f1eefb5 on kubedog's 0 branch, which releases those informers (werf/kubedog#407, backport of werf/kubedog#406). The range also brings werf/kubedog#405, which fixes the resource elimination wait of the legacy release uninstall path.

What

  • go.mod/go.sum: github.com/werf/kubedog v0.13.1-0.20260912145640-ad1e8a134607 → v0.13.1-0.20261103161329-f1eefb59d19a; no other module changes.
  • Kubedog range ad1e8a1..f1eefb5 is two commits: werf/kubedog#405 and werf/kubedog#407.

Tracking during release install / release rollback / native release uninstall (werf/kubedog#407)

  • After resource tracking ends, the shared informers started for it stop and release their caches, including when the tracking side stops reading events mid-stream. Before, a handler blocked on a send kept the informer and its cache alive for the life of the process; most often the ReplicaSet informer of a Deployment.
  • While tracking runs, every event is delivered as before: channel capacities and send order are unchanged, nothing is dropped.
  • A fatal watch error raised after tracking stopped no longer blocks the informer from stopping.
  • When starting a Deployment, StatefulSet, DaemonSet, Job or Pod tracker fails halfway, the informers it already started are released.
  • Not changed: Deployment failure handling. The fail-fast on ReplicaSet pod-create errors from kubedog main (38643e9) is not part of kubedog's 0 branch and does not come with this bump.
  • UNVERIFIED: the leak fix is not reproduced against a real cluster here; kubedog covers every affected handler with regression tests on a fake dynamic client.

Resource elimination wait in the legacy uninstall path (werf/kubedog#405)

  • Applies to nelm release uninstall without NELM_FEAT_NATIVE_RELEASE_UNINSTALL/NELM_FEAT_PREVIEW_V2, and to action.LegacyReleaseUninstall callers, at the Waiting for resources elimination step.
  • The wait no longer misses a deletion that happens between its initial LIST and WATCH, which made it run until the timeout.
  • A consumer that builds nelm v1 with client-go v0.35+ (where the WatchListClient feature gate is on by default) no longer hangs at Waiting for resources elimination until the timeout when the resources are already gone. nelm itself pins client-go v0.29.3, where the gate is off.

Why

Kubedog's informer event handlers on 0 sent to tracker channels without watching for cancellation. Once the tracker stopped reading, a handler blocked forever, so the stopped informer waited on it and never returned, keeping its namespace-wide cache referenced; in a process that deploys repeatedly this accumulated into gigabytes. The elimination tracker replaced the reflector's list/watch options with a bare field selector, dropping the resourceVersion and WatchList parameters, which caused both the missed deletion and the WatchList hang.

BEGIN_COMMIT_OVERRIDE
fix: stop leaking informers and their caches after tracking
fix: stop resource elimination waiting from missing deletions and hanging when WatchListClient is enabled
END_COMMIT_OVERRIDE