Unpin Forgejo runners from kai-desktop-tower-wsl (remove obsolete SSH-era nodeSelector) #241
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#241
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?
Both Forgejo Actions runner StatefulSets (
deploy/forgejo-runner.yml,deploy/forgejo-runner-tap-writer.yml) carriednodeSelector: kubernetes.io/hostname: kai-desktop-tower-wsl, pinning the entire CI runner tier to a single WSL node on the desktop tower. When that node wentNotReady(2d+, see coilysiren/inbox#65) all flight-deck CI went dark with no failover.The pin originally existed to work around an SSH networking problem that is believed no longer to apply. Remove the
nodeSelectorfrom both so runners schedule on any Ready node (today:kai-server, the control-plane, which k3s leaves schedulable).Follow-up: if SSH-dependent jobs break after this, the pin's original reason still holds and we hard-pin to
kai-serverinstead. Always-on hardening for the WSL node tracked separately.