Route the dev session as QUIC over UDP 7400
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 5s
Foundation / checks (postgres) (push) Successful in 5s
Foundation / checks (tsan) (push) Successful in 5s
Foundation / checks (deploy) (push) Successful in 3m16s
Foundation / postgres-tools (push) Successful in 5s
Foundation / server-image (push) Successful in 5s
Foundation / image (push) Successful in 6s

The deployed M10 listener is QUIC (UDP) but the ADR-0087 route admitted only TCP
7400, so nothing reached it through the VIP. The route container port, Service and
NetworkPolicy now carry UDP 7400 only (no TCP: nothing needs it). The policy check
requires exactly UDP 7400 for the route and counts any protocol on 7400 as session
exposure elsewhere; six new self-test cases. ADR-0087 amended (edge firewall and
internal DNS as separate reviewed steps, end-to-end probe as acceptance);
session protocol v1 recorded as frozen now that it is deployed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
dingo
2026-10-05 17:04:31 -04:00
co-authored by Claude Opus 5.5
parent 5caed552b9
commit d917e8443d
11 changed files with 106 additions and 27 deletions
+19
View File
@@ -4309,3 +4309,22 @@ session and network tests; Windows MSVC 19.44 preset `quic` build (including the
CTest 4/4 (binaries rebuilt, timestamps checked).
Not done: the engineering GUI client on M10 sessions; packaging (the server image does not
enable QUIC); a two-process cross-region move; ASan of the PostgreSQL suite.
## 2026-10-05 — Dev session route moved to UDP 7400 for QUIC (ADR-0087 amendment)
Finding: the deployed M10 QUIC listener (UDP) sat behind a route that admitted only TCP
7400 (container port, Service, NetworkPolicy, policy check). Pod-side checks (ready,
listener bound on 7400) could not detect it. Also found: `void.aeternalisgames.com`
resolves to 172.10.1.160 (control plane) from the workstation, not the VIP 172.10.1.202.
Changed: route container port, Service and NetworkPolicy to UDP 7400 only; policy check
(route exactly UDP 7400, UDP container port, any-protocol session exposure elsewhere) and
six new self-test cases; ADR-0087 amendment; session-v1 frozen note.
Executed: `tools/ci/deploy-policy-check.py` (71 objects in 69 files, 130 rendered objects
in 17 overlays, 0 failures) and `tools/ci/deploy-policy-selftest.py` (44 cases, all
refused) with pinned kustomize v5.8.1, before (38 cases) and after; rendered region/dev
inspected: Service `evo-region-session` UDP 7400 only on 172.10.1.202 with source range
172.10.1.0/24, `Local`, no node ports; NetworkPolicy UDP 7400 from 172.10.1.0/24; pod
port `session` UDP 7400; no other Service exposes 7400.
Not done (needs the maintainer): Argo sync of this change; the edge firewall rule;
internal DNS to 172.10.1.202; retrieving the dev CA and issuer key (no cluster credentials
on the workstation); the end-to-end probe through the VIP. The route is not verified.