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
+5
View File
@@ -37,6 +37,11 @@ evo-server QUIC listener (session control and action records under the host's le
the headless `evo-session-probe`, with real-process tests including SIGKILL before and after
an action's commit. M10.4 is complete; the GUI client still uses the M9 dev path. Next:
M10.5 bounded snapshots and spatial interest.
Deployment (2026-10-05): the maintainer deployed the M10 QUIC listener to evolution-dev
behind the ADR-0087 route; session protocol v1 is therefore frozen. The route admitted
only TCP 7400 while QUIC is UDP, so it is changed to UDP 7400 (ADR-0087 amendment). The
route is not yet verified end to end: the edge firewall rule (UDP 7400 from
172.10.1.0/24), internal DNS to 172.10.1.202 and a probe run through the VIP remain.
## Previous gate - 2026-10-02
+30 -4
View File
@@ -13,8 +13,9 @@ Internal testers need the native client (M9.8e ZIP) to reach the dev region with
`kubectl port-forward`. The cluster inventory (INVENTORY.md, 2026-09-29) shows RKE2's
ingress-nginx 1.12.1 DaemonSet serving 80/443 on all four node addresses (public sites
included), MetalLB 0.15.2 in FRR mode with one LoadBalancer (Gitea SSH), and an existing
HTTP Ingress for void.aeternalisgames.com in namespace `void`. The session protocol is
TLS 1.3 over raw TCP (ADR-0082), not HTTP. Sessions need synthetic carrier inputs, which
HTTP Ingress for void.aeternalisgames.com in namespace `void`. The session protocol was
TLS 1.3 over raw TCP (ADR-0082) when this was written; since 2026-10-05 the route carries
the M10 session, QUIC over UDP (ADR-0090/0091/0092; amendment below). Never HTTP. Sessions need synthetic carrier inputs, which
ADR-0073 keeps drill-time only so dev history does not grow continuously.
## Decision (maintainer, 2026-10-02)
@@ -35,8 +36,8 @@ reach only a ready pod; after a replacement, clients reconnect with a fresh gran
baseline (ADR-0083).
**Access.** Development workstation/test subnet only, in three layers: the edge
firewall, the Service source ranges and a NetworkPolicy admitting TCP 7400 to the region
pod from exactly those CIDRs. TLS with the dev CA and single-use, short-lived grants stay
firewall, the Service source ranges and a NetworkPolicy admitting UDP 7400 (QUIC; TCP 7400
until 2026-10-05) to the region pod from exactly those CIDRs. TLS with the dev CA and single-use, short-lived grants stay
mandatory; grants remain bearer tokens.
**Listener.** The base keeps the opt-in listener on loopback through
@@ -121,3 +122,28 @@ cannot enable listeners, sessions, inputs or session ports outside the route.
One reviewed exception to "no LoadBalancer" for evolution-dev. The policy check and its
fail-closed self-test (`tools/ci/deploy-policy-selftest.py`) encode the route's shape and
the enabling preconditions. World0 and stage are untouched.
## Amendment 2026-10-05: QUIC over UDP 7400 (maintainer)
The deployed listener is the M10 QUIC session (`--m10-listen`, ADR-0092), which is UDP. The
route still admitted only TCP 7400 (container port, Service, NetworkPolicy and the policy
check), so nothing reached the listener through the VIP, and nothing listened on TCP 7400;
the pod-side checks (ready, listener bound) could not show this. Decision:
- The route carries **UDP 7400 only**: container port, `evo-region-session` port and the
session NetworkPolicy. TCP 7400 is removed, not kept beside it: no supported protocol
needs it (the M9 TLS-over-TCP session is no longer wired into the deployment). The
Service has a single protocol, so MetalLB mixed-protocol support is not involved; the
VIP, `Local` traffic policy, no node ports, source ranges and the health-check note are
unchanged.
- `deploy-policy-check.py` requires exactly UDP 7400 for the route and a UDP container
port, and counts any protocol on 7400 (UDP, TCP, SCTP) as exposure of the session port
for every other policy and Service; the self-test refuses stale TCP route objects, TCP
beside UDP, and other policies admitting UDP or SCTP 7400.
- **Edge firewall: separate, explicitly reviewed change**, outside the repository: allow
UDP 7400 to 172.10.1.202 from 172.10.1.0/24 only, never a wider source range. Internal
DNS must resolve `void.aeternalisgames.com` to the VIP 172.10.1.202 (enabling step 4);
on 2026-10-05 it resolved to the control-plane address 172.10.1.160.
- **Acceptance** is end to end, not pod-side: `evo-session-probe` from 172.10.1.0/24
succeeds through `void.aeternalisgames.com:7400 -> edge firewall -> MetalLB VIP ->
Service UDP 7400 -> NetworkPolicy UDP 7400 -> evo-region M10 listener`, with the dev CA
and issuer key read from the authorized cluster Secret without printing or persisting
them. Until that is recorded in VALIDATION.md the route is not declared working.
@@ -50,6 +50,7 @@ duplicates and queries; older ones are resolved from the durable record (10.4b).
**Protocol.** Session protocol v1 gains message types 6-12 and Welcome gains the server
tick (schemas/network/session-v1.md). v1 has never been deployed, so it is amended in
place, as ADR-0083 did for M9 v1; after its first deployment, changes need a new version.
v1 was deployed in evolution-dev on 2026-10-05 and is frozen from then on.
The action kind is a raw u16 on the wire and validated by admission (an enum narrower than
the wire field must never be cast from it).
+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.