Add M9.8f dev session route design, disabled with fail-closed policy

ADR-0087 records the maintainer's route (void.aeternalisgames.com:7400 via a
dedicated internal MetalLB VIP to the evolution-dev region pod, TLS end to end,
CIDR-limited) and operator-opened windows enforced by evo-server. The route is a
kustomize component included nowhere; the policy check encodes its shape and
refuses enabling until VIP/CIDR, the dev quota and --session-window exist, with a
20-case self-test in the CI deploy stage. The base listener stays loopback.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
dingo
2026-10-02 17:34:12 -04:00
co-authored by Claude Opus 5.5
parent 2a2d6fbbfe
commit 9f622cf6b3
18 changed files with 504 additions and 24 deletions
+7 -4
View File
@@ -4,7 +4,9 @@ Status: M9.8a probe, M9.8b owned state/capture/event bounds, M9.8c launcher,
legend, labelled inspector and click selection, and M9.8d rebindable controls
complete, 2026-10-02. M9.8e local Windows ZIP complete (ADR-0086); its Gitea
Actions publication waits for a Windows runner and its clean-VM run for M9.8g.
Remaining segments planned.
M9.8f route design, disabled manifests and fail-closed policy tests complete
(ADR-0087); enabling waits for the VIP, client CIDR, DNS, dev quota and server-enforced
session windows. M9.8g remains.
No application UI or deployment completion is claimed. See ADR-0084 for the toolkit boundary.
## Confirmed scope
@@ -64,9 +66,10 @@ All selected biological data remains a read-only presentation copy.
- No Windows runner exists yet (confirmed 2026-10-02). Local builds are the initial path. Do not silently route a Windows
package job to the existing Linux runner or assume an untested cross-compile.
The packaging script can run on the existing Windows development host meanwhile.
- Confirmed control plane: 172.10.1.160. Still needed for direct service routing:
nginx implementation/configuration, exposed TCP port,
source restrictions and certificate name. The protocol is TLS/TCP, not HTTP;
- Confirmed control plane: 172.10.1.160. Direct routing decided in ADR-0087: dedicated
internal MetalLB VIP, TCP 7400, void.aeternalisgames.com, CIDR-limited. Still needed:
the VIP from the MetalLB pool, the permitted client CIDR, internal DNS, and decisions
on Argo delivery of session windows and the existing void HTTP Ingress. The protocol is TLS/TCP, not HTTP;
a standard HTTP Ingress rule does not implement it. Port-forward remains supported.
- VM specification and whether graphics acceleration is available. Hardware-specific
performance acceptance cannot be declared before these are known.
+34
View File
@@ -3896,3 +3896,37 @@ Executed on the Windows development host (MSVC 19.44.35217, CMake 3.31.6):
Not done: Gitea Actions publication (no Windows runner), a run on a clean Windows
VM (M9.8g), code signing, hardware/DPI qualification, legal review of notices.
## 2026-10-02 — M9.8f dev session route design (ADR-0087)
Maintainer decisions: dedicated internal MetalLB VIP, TCP 7400,
void.aeternalisgames.com, TLS ending in the region pod, development/test CIDR only
(firewall + Service source ranges + NetworkPolicy), no Ingress/nginx TLS/PROXY
protocol; operator-opened windows with server-enforced absolute expiry; scope limited
to design, manifests and policy tests. Nothing was applied to the cluster.
Implemented: `REGION_SESSION_LISTEN` (base stays 127.0.0.1:7400); the disabled
component `deploy/kubernetes/region/dev-session-route` (LoadBalancer Service with
Local policy, no node ports, pinned VIP annotation and source ranges; CIDR-only
ingress policy on TCP 7400; listener patch to the pod interface) carrying REPLACE
markers; policy rules for the route's exact shape, LoadBalancer/NodePort and
session-port exclusivity, no session Ingress, evolution-dev-only placement, quota
limits, and enabling preconditions (no markers, dev quota of exactly one
LoadBalancer, server `--session-window`); patch files are now recognized generally.
`tools/ci/deploy-policy-selftest.py` copies the manifests and applies 20 unsafe changes.
Executed (WSL Ubuntu, Python 3 with PyYAML 6.0.1): deploy policy check on the
repository, 70 objects in 68 files, 0 failures; self-test 20/20 refused, baseline
copy passes; ops-lib and ci-path fixtures pass; session-drill usage unchanged.
kustomize v5.4.3 (official release, SHA-256 checked against its checksums.txt, in a
scratch directory, not a project dependency) rendered region/dev as committed (listener
127.0.0.1:7400, no session Service) and a temporary enabled copy with example private
values (LoadBalancer evo-region-session and the CIDR policy in evolution-dev, listener
0.0.0.0:7400, session container port merged).
Not run: the ci-deploy Docker stage (no Docker in this WSL distribution; its commands
were run directly), any cluster/server dry-run, MetalLB allocation, DNS, firewall or live
connectivity. Server-enforced session windows and the Gitea window workflow are not
implemented; Argo delivery for windows and the existing void HTTP Ingress are open
maintainer decisions recorded in ADR-0087.