Jinwoo Hong 99e91c16ae fix(relay): give each director revision its own instance maximum instead of a split service cap (#31178) ...

The deploy passed `--max`, which is gcloud's service-wide cap. Cloud Run divides
that cap among the revisions taking traffic, so during the 20/80 stage a
candidate under a cap of 5 got one instance while the serving floor kept four,
and the spread check could never see the full floor (deploy M, 1 of 5 for six
minutes). Candidates now pin `--max-instances` per revision, and the deploy
resets a service cap below two full revisions to Cloud Run's default before it
creates any candidate. The rollout overlap of two full directors is already in
the checked Cloud SQL connection budget.

2026-10-20 13:47:38 -04:00

..

contracts

infra(relay): raise asia-east2 cell pools to 16 and record the measured connection ceiling (#21163)

2026-09-17 02:00:17 -04:00

fixtures/terraform-root-partition

fix(relay): move director traffic in two steps so a deploy does not land on one instance (#31051)

2026-10-20 04:13:17 -04:00

scripts

fix(relay): give each director revision its own instance maximum instead of a split service cap (#31178)

2026-10-20 13:47:38 -04:00