Warm-standby: decide home-2 sync for kai-server host-side game-server saves (out of k3s) #265
Labels
No labels
burndown-2026-06
burndown-2026-08
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/advocate
role/director
role/exec
role/frontend
role/gamedev
role/human
role/platform
role/qa
role/science
role/sysadmin
state
ambient
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/infrastructure#265
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Warm-standby follow-up (from the
machine-kai-ser8skill, not ticketed in #99). The host-side systemd game servers on kai-server (Eco, Factorio, Icarus, Core Keeper) are not in k3s, so the k3s snapshot-ship path misses their saves entirely.Decide: do their saves get a home-2 sync (separate rsync/timer to ser8), or are they explicitly out of DR scope? Document the decision either way so the gap isn't silent. If in scope, the Factorio backup already has
scripts/factorio-backup.shto build on.Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag:
burndown-2026-06.