Jinwoo Hong bf8d63bc67 fix(relay): keep the backend service out of the same-cap wave; the capacity role cannot update it (#22140) ...

The capacity role the same-cap wave authenticates as, orcaRelayProductionCapacity,
has no compute.backendServices.update. Since #21860 added
`google_compute_backend_service.relay_gce_cell["${TARGET_CELL_ID}"]` to both of the
job's plan invocations, every wave has therefore created the new instance template,
modified the MIG, and then failed 403 on the backend, leaving the cell isolated with
its trust probe, admission restore, and shadow gate all skipped. Run 35684694704 on
production-gce-c7 is the first one that hit it in production.

Drop the backend target from both plans and restore the resume gate to exactly
`.changes == 2` (the template-and-MIG rollback-image drift) or a converged plan,
removing the backend-only resume apply #21865 added on top. A resume applies nothing
again, which is what a resume means.

The validator keeps its bound on a cell backend update, so it still reports one and
refuses anything wider, but a wave plan can no longer contain one. The drain timeout
from #21848 and the log_config from #21860 need a root apply by a principal that holds
the permission; granting the capacity role that permission is itself a root apply, so
it can follow as its own change rather than blocking every wave in the meantime.

Claude-Session: ced32ebb-7155-4413-adad-1eccd14c2010

2026-09-22 02:50:32 -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

feat(cloud): native push gateway and dedicated infrastructure (1/3) (#19912)

2026-09-10 17:59:46 -04:00

scripts

fix(relay): keep the backend service out of the same-cap wave; the capacity role cannot update it (#22140)

2026-09-22 02:50:32 -04:00