feat(relay): add syd (Sydney) region to relay fleet

Merged
KI
4mo ago
+3-3

What

Adds Fly's Sydney region (syd) to the relay fleet, bringing it to 7 machines, 1 per region: sjc (primary), iad, fra, nrt, sin, syd, gru.

Why

The relay fleet is driven entirely by the REGIONS array in apps/relay/scripts/deploy.sh — the relay reads FLY_REGION dynamically and fly-replay routes by region string, so there's no client-side allowlist to touch.

Australian users previously had no closer relay than sin/nrt. When their remote host lands in a Sydney-adjacent Fly region, the region mismatch surfaces as a relay 502 on WebSocket upgrades (fly-replay isn't transparent for WS upgrades). A syd machine gives AU traffic a local relay and closes that gap.

Changes

  • apps/relay/scripts/deploy.sh — add syd to REGIONS (6 → 7)
  • apps/relay/fly.toml — update topology comment

Rollout

Run apps/relay/scripts/deploy.sh: the fly scale count "app=7" --region ... --max-per-region 1 step provisions the Sydney machine, followed by the rolling deploy and smoke test (which now covers syd).

Open in Stage

Summary by cubic

Add syd (Sydney) to the relay fleet, bringing it to 7 regions with 1 machine each. This gives AU users a local relay and reduces WebSocket 502s caused by region mismatches.

  • Migration
    • Run apps/relay/scripts/deploy.sh; it scales to 7 regions (adds syd), deploys, and runs smoke tests.

Summary by CodeRabbit

  • Chores
    • Expanded deployment coverage to an additional region.
    • Updated scaling settings so the service now starts with one more machine, improving regional availability and consistency.