vikingowl f83d73c06d fix(deploy): set maxSurge=0 to fit within ResourceQuota during rollout ...

With 900m/1000m CPU limits used, rolling updates fail because the
new pod cannot be created alongside the old one. Setting maxSurge=0
and maxUnavailable=1 kills the old pod first, avoiding quota exhaustion
at the cost of brief downtime during deploys.

2026-02-22 12:00:23 +01:00

web

fix(deploy): set maxSurge=0 to fit within ResourceQuota during rollout

2026-02-22 12:00:23 +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%