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

Ghost node: kai-desktop-tower duplicates kai-desktop-tower-wsl in k3s #13

New issue
Closed
opened 2026-05-23 20:54:27 +00:00 by coilysiren · 1 comment
coilysiren commented 2026-05-23 20:54:27 +00:00
Owner
Copy link

Originally filed by @coilysiren on 2026-05-22T13:15:23Z - https://github.com/coilysiren/infrastructure/issues/275

Symptom - kubectl get nodes shows kai-desktop-tower as NotReady (28d) alongside kai-desktop-tower-wsl as Ready (8d).

The two entries are the same physical machine. Identical kernel (5.15.167.4-microsoft-standard-WSL2), identical container runtime, and both claim the same INTERNAL-IP 172.27.244.126. The older kai-desktop-tower entry is a stale registration left behind when the node was renamed to kai-desktop-tower-wsl.

Fix - delete the ghost: kubectl delete node kai-desktop-tower. Confirm nothing references the old name (manifests, nodeSelectors, deploy scripts) before deleting.

Found while setting up a Lima-based Mac node, inspecting how existing nodes join the cluster.

_Originally filed by @coilysiren on 2026-05-22T13:15:23Z - [https://github.com/coilysiren/infrastructure/issues/275](https://github.com/coilysiren/infrastructure/issues/275)_ **Symptom** - `kubectl get nodes` shows `kai-desktop-tower` as NotReady (28d) alongside `kai-desktop-tower-wsl` as Ready (8d). The two entries are the same physical machine. Identical kernel (`5.15.167.4-microsoft-standard-WSL2`), identical container runtime, and both claim the same INTERNAL-IP `172.27.244.126`. The older `kai-desktop-tower` entry is a stale registration left behind when the node was renamed to `kai-desktop-tower-wsl`. **Fix** - delete the ghost: `kubectl delete node kai-desktop-tower`. Confirm nothing references the old name (manifests, nodeSelectors, deploy scripts) before deleting. **Found while** setting up a Lima-based Mac node, inspecting how existing nodes join the cluster.
coilysiren commented 2026-06-17 08:22:59 +00:00
Author
Owner
Copy link

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.

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`.
coilysiren 2026-06-17 08:23:00 +00:00
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#13
No description provided.