vikingowl fd879ba026 fix(deploy): use maxSurge=0 for rolling update to fit resource quota ...

maxSurge=1 requires a second pod during rollout, but the tenant
ResourceQuota (1 CPU limit) is already at 900m — the extra 250m
exceeds the cap and the pod can't schedule, causing a 5min timeout.

Switch to maxSurge=0/maxUnavailable=1 (kill-then-start) to stay
within quota. Matches the web deployment strategy.

2026-02-27 14:17:02 +01:00

backend

fix(deploy): use maxSurge=0 for rolling update to fit resource quota

2026-02-27 14:17:02 +01:00

Description

No description provided

1.7 MiB

Languages

Go 60.3%

Svelte 20.3%

Dart 11.1%

TypeScript 5%

PLpgSQL 1.1%

Other 2.1%