Haven Xia d0d85c397d atecontroller: set the worker Deployment rollout strategy (#1783) ...

The Kubernetes default strategy (`maxSurge=25%, maxUnavailable=25%`) can
stall small pools when a workerpool edit and get k8s deployment rolling:

below 4 replic, as `maxUnavailable` rounds to 0, the surge pod needs to
land first, and if existing pods already take all spaces of their node,
the new one never lands and the rollout is stuck.

Use `maxSurge` 0 with `maxUnavailable` 10%, which Kubernetes will
evaluate as removing remove least one pod first so it will never block.

Also modify `progressDeadlineSeconds`to be 3600s so a batch waiting out
the drain window (currently 30min) is not reported as a failed rollout.

- [ ] Tests pass
- [ ] Appropriate changes to documentation are included in the PR

2026-09-22 12:07:59 +00:00

..

internal

atecontroller: set the worker Deployment rollout strategy (#1783)

2026-09-22 12:07:59 +00:00

main_test.go

feat(otel): onboard atecontroller to the OTLP path (#754)

2026-08-06 10:25:03 -04:00

main.go

Fix propogate issue to workers with worker pools changes (#1636)

2026-09-14 11:22:20 -04:00