Allow four-hour dev session windows
Foundation / checks (client) (push) Successful in 12m45s
Foundation / checks (deploy) (push) Successful in 6s
Foundation / checks (ecs) (push) Successful in 1m56s
Foundation / checks (network) (push) Successful in 9m59s
Foundation / checks (postgres) (push) Successful in 39m8s
Foundation / checks (tsan) (push) Successful in 7m57s
Foundation / checks (checks) (push) Failing after 10m55s
Foundation / postgres-tools (push) Skipped
Foundation / server-image (push) Skipped
Foundation / image (push) Skipped
Foundation / checks (client) (push) Successful in 12m45s
Foundation / checks (deploy) (push) Successful in 6s
Foundation / checks (ecs) (push) Successful in 1m56s
Foundation / checks (network) (push) Successful in 9m59s
Foundation / checks (postgres) (push) Successful in 39m8s
Foundation / checks (tsan) (push) Successful in 7m57s
Foundation / checks (checks) (push) Failing after 10m55s
Foundation / postgres-tools (push) Skipped
Foundation / server-image (push) Skipped
Foundation / image (push) Skipped
This commit is contained in:
@@ -45,11 +45,13 @@ mandatory; grants remain bearer tokens.
|
||||
session port. The listener still starts only when sessions are enabled.
|
||||
|
||||
**Windows.** Sessions and synthetic inputs run only during an operator-opened test window
|
||||
with automatic expiry (default 30 minutes); always-on simulation waits for an explicit
|
||||
disposable-world lifecycle and retention. The endpoint (DNS, MetalLB Service) may stay
|
||||
configured permanently. A small dev-only GitOps configuration holds an activation id,
|
||||
with automatic expiry. The maintainer decision on 2026-10-05 sets four hours as both the
|
||||
operator workflow's default and the server's maximum accepted duration; always-on
|
||||
simulation waits for an explicit disposable-world lifecycle and retention. The endpoint
|
||||
(DNS, MetalLB Service) may stay configured permanently. A small dev-only GitOps
|
||||
configuration holds an activation id,
|
||||
the exact world/region identity and an absolute UTC expiry. Operations, via a manually
|
||||
triggered Gitea workflow: Open (default 30 min), Extend (new explicit expiry), Close
|
||||
triggered Gitea workflow: Open (default four hours), Extend (new explicit expiry), Close
|
||||
(stop accepting sessions, close existing connections, stop synthetic inputs, drain
|
||||
pending commits) and Status (window, expiry, active sessions, committed tick).
|
||||
Expiry is enforced **inside evo-server**, not by a delayed cleanup job:
|
||||
@@ -92,8 +94,7 @@ pending until applied, with an absolute expiry that delayed sync never shifts (C
|
||||
also needs propagation; the server deadline is the upper bound); keep the existing void
|
||||
HTTP endpoint unless explicitly retired, possibly choosing a dedicated session hostname
|
||||
instead (DNS cannot select by TCP port), before issuing the certificate; confirm the
|
||||
actual MetalLB pool and client addresses; set the maximum window length and clock
|
||||
handling before implementing windows.
|
||||
actual MetalLB pool and client addresses; clock-skew handling remains open.
|
||||
|
||||
- **Argo delivery.** The aevolution-dev Application has no automated sync, and the
|
||||
policy forbids auto-sync outside the platform app (ADR-0069). A workflow commit alone
|
||||
@@ -103,7 +104,7 @@ handling before implementing windows.
|
||||
- **void namespace.** void.aeternalisgames.com already has an HTTP Ingress (namespace
|
||||
`void`). Pointing internal DNS at the VIP changes what internal clients reach for that
|
||||
name; confirm or retire the existing route.
|
||||
- Window limits: maximum window length and clock-skew tolerance.
|
||||
- Clock skew: the four-hour maximum is decided; define the permitted clock-skew tolerance.
|
||||
|
||||
## Alternatives considered
|
||||
- ingress-nginx tcp-services or SNI passthrough on 443: couples game sessions to the
|
||||
|
||||
Reference in New Issue
Block a user