coilyco-flight-deck/infrastructure
2
0
Fork 0
Code Issues 118 Pull requests Projects Releases Packages Wiki Activity Actions 2

Unpin Forgejo runners from kai-desktop-tower-wsl (remove obsolete SSH-era nodeSelector) #241

New issue
Closed
opened 2026-06-06 05:11:23 +00:00 by coilysiren · 0 comments
coilysiren commented 2026-06-06 05:11:23 +00:00
Owner
Copy link

Both Forgejo Actions runner StatefulSets (deploy/forgejo-runner.yml, deploy/forgejo-runner-tap-writer.yml) carried nodeSelector: 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 went NotReady (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 nodeSelector from 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-server instead. Always-on hardening for the WSL node tracked separately.

Both Forgejo Actions runner StatefulSets (`deploy/forgejo-runner.yml`, `deploy/forgejo-runner-tap-writer.yml`) carried `nodeSelector: 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 went `NotReady` (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 `nodeSelector` from 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-server` instead. Always-on hardening for the WSL node tracked separately.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
issue-515
issue-486
issue-529
issue-500
issue-483
No results found.
Labels
Clear labels   
burndown-2026-06
Backlog burndown June 2026

  
coherence-core
Core review set for the warded control plane coherence milestone. These issues form the release spine; adjacent milestone issues are stretch or supporting work.

  
consult
A human decision, design, or external action must happen first. Fail-closed default for unlabeled/low-confidence.

  
headless
Agent can take it from open issue to merged change with no human in the loop. The auto-burndown queue.

  
interactive
Agent does the work but pauses at a human checkpoint mid-flight (design choice, destructive step, human-only verification).

  
P0
now / blocking / urgent

  
P1
next / important

  
P2
backlog / will do

  
P3
someday / low

  
P4
icebox / frozen / reopen if it becomes real

No labels
burndown-2026-06
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
coilyco-flight-deck/infrastructure#241
No description provided.