flyemoji
096d59716e
Retroactively author 15 grouped detail docs covering the backend functional (feat/fix) commits made before the change ledger was established (fad48ff), closing the ledger's detail-doc axis for the pre-convention history. Each doc groups a feature's constituent commits, lists their SHAs with subjects, and carries a backfill note stating it was reconstructed from git history on 2026-07-07 and not independently re-verified (current tree green at9911b8c). Add a Detail docs section to INDEX.md linking every detail doc (the 6 existing + 15 backfill) to the commit(s) it covers, so a doc is findable from the index without a column on the auto-generated ledger table. Catch the table up with the missing9911b8crow. Scope: backend (Go/Java/K8s) only, per the ledger's stated convention that frontend/panel commits are the collaborator's UI work; non-functional commits (docs/style/chore/refactor) keep their table row without a dedicated detail doc.
2.9 KiB
System servers: login-limbo + lobby (always-on gate) (ledger backfill)
- Type: feature — retroactive ledger entry
- Date: 2026-07-02
- Area:
internal/config,internal/naming,internal/api(CRD readiness),internal/operator,internal/platform,cmd/felis,plugins/limbo,deploy/limbo+deploy/lobby - Commits:
9bed51bfeat(config):[velocity] login_image/lobby_image— setup provisions the always-on system services only when set (empty = fail-loud skip; no official LOOHP/Limbo image exists)9ef817ffeat(naming): reserved system-server names + service-token identifiers (single source of truth for the internal-API credential Secret)159107bfeat(api): HTTP readiness knob onMinecraftServer+ user-server fallback defaults to the login gatedc23cb5feat(operator): system-server pod HTTP readiness probe + login-onlyFELIS_SERVICE_TOKENenv (keyed off the reserved name so it can never leak into a user pod; sourced viasecretKeyRef, never inlined)3fdb3d0feat(platform): internal-API base-URL helper + single-sourced token Secretf554d52feat(cli): provision the reaper-exempt login/lobby servers + replicate the service-token Secret into the minecraft namespace241fe21feat(limbo): felis-limbo in-game login flow (join → blacklist check → mint bind code → open book toconsole.<root_domain>→ poll link-status → BungeeCord transfer to lobby; fail-closed)c7315e4feat(deploy): login-limbo + lobby images with game-port pinning (server-port pinned to GamePort 25565 on every start)
- Tasks: #53–#68 (system-server plumbing L1–L4, limbo plugin, operator env injection)
What it did
Stood up the always-on authentication gate: reserved, reaper-exempt login/lobby
MinecraftServers provisioned by setup, an HTTP readiness path for the RCON-less LOOHP/Limbo
loader (which reports "started" only after the first tick), and the felis-limbo plugin that
runs the whole onboarding inside Limbo before transferring an admitted player to the
lobby. A fresh connection always lands on the login gate, never a user backend, so
authentication is always in front.
Why
The spec requires that a player authenticate before reaching any real server. That needs a purpose-built always-on front server (Limbo) that speaks to the internal API — hence the login-only service-token injection (keyed to the reserved name so it can never reach a user pod) and the HTTP readiness knob for a loader that has no RCON.
Backfill note. Reconstructed 2026-07-07 from the commit history. The Go layer (config/naming/readiness/operator env/platform) was unit-tested at each commit; the felis-limbo plugin is Java verified against a real Limbo jar via podman (#65), and the images carry a real build+boot check (#63, limbo
/healthz200 on 25565). Not independently re-verified for this doc; current tree green at9911b8c.