IvanHunters 3d1a83f419 fix(migrations): make the unadopted-pools record publish best-effort ...

The durable-record ConfigMap write sat under set -euo pipefail right before the
version stamp, so a permanent failure (e.g. the record exceeding etcd's object
size limit at a very large skip count) would abort the migration and deadlock
the fleet upgrade with no path out -- even though every skipped pool was already
pinned prune-proof earlier in the sweep, so the workers are safe regardless of
whether the record lands. The record is a convenience artifact, not a safety
mechanism, so swallow its failure with a warning instead of failing closed.
Covered by a bats case that fails the publish and asserts the run still stamps.

Signed-off-by: IvanHunters <xorokhotnikov@gmail.com>

2026-08-25 12:38:28 +03:00

..

kubectl

fix(migrations): make the unadopted-pools record publish best-effort

2026-08-25 12:38:28 +03:00