chore: bump kubedog to fail fast on ReplicaSet pod-create errors
Merged
IL
24d ago+3+3+0123456789-3-3-0123456789
Summary
Bumps github.com/werf/kubedog to the merge commit of werf/kubedog#404 on kubedog main (97f4f13), which makes Deployment tracking fail fast on ReplicaSet pod-create errors such as exceeded quota (werf/kubedog#398).
werf/kubedog#404 is merged; this PR pins its merge commit.
What
go.mod/go.sum:github.com/werf/kubedogv0.13.1-0.20260915153156-438ef109f804→v0.13.1-0.20261029011008-97f4f131413e.- The bump also brings in the kubedog
maincommits since the previous pin (438ef10..b201189): golangci-lint cleanups and reformatting. They do not change behaviour. - It also brings in hardening from werf/kubedog#404: quota quantities parsed from a
FailedCreatemessage are bounded, so a crafted ReplicaSet status cannot keep the tracker busy.
Why
Without this bump, nelm (and werf) keep waiting for the tracking timeout when a Deployment's new ReplicaSet cannot create pods. The failure is only visible in ReplicaSet events.
Behaviour changes for nelm users
These come from pkg/dyntracker, which pkg/plan/plan_execute.go uses:
- An invalid pod spec, or a quota deadlock the rollout cannot resolve on its own, now fails the resource immediately, regardless of
werf.io/failures-allowed-per-replica. A quota deadlock is reported about 10s after it is observed, with theFailedCreate ... exceeded quotadiagnostic. - Other pod-create failures, including quota failures that the rollout can recover from, are added once as errors against the failures budget. Before, they were not seen at all.
- With
werf.io/fail-mode: IgnoreAndContinueDeployProcess, these fatal failures do not fail the deploy. - Only ReplicaSets controlled by the Deployment are treated as its new ReplicaSet. An orphan ReplicaSet that matches the template is ignored until the Deployment adopts it.
- A Deployment failure from an event is charged to the budget once, not again on every later status update.
- Fast-failing on a quota deadlock needs
list pods(already needed for tracking) andget resourcequotasin the namespace. The built-inview,editandadminroles have both. Without them, quota failures are counted rather than fatal.
Testing
task build,task test:unit(67 suites) andtask lintpass.- The kubedog PR has unit tests for each case and was verified on kind with a
ResourceQuota, tracking throughdyntrackeras nelm does.