Evacuate CI runners from kai-server to the ser8 cluster #314
Labels
No labels
burndown-2026-06
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
coilyco-flight-deck/infrastructure#314
Loading…
Add table
Add a link
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?
Mitigation 1 from #311 (assumes the k3s ExecStartPre stays). Forgejo runners only need network reach to forgejo, not co-location with it. Running them on ser8's k3s removes them from kai-server's k3s restart blast radius entirely, so the recurring CI-down-after-maintenance failure mode stops existing. Also aligns with the strategic split: kai-server hosts apps, ser8 hosts the ops plane. Depends on ser8's k3s standing up (the o11y baseline work).