Orphan-reaper for kai-server: reap PPID-1 container payloads holding stale locks #316
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#316
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 3 from #311. The disease is deterministic so the cure scripts cleanly: find PPID-1 processes whose cgroup maps to no live pod, confirm they hold the contested lock, kill them, delete the crashlooped pods. Two deployment shapes that leave k3s config untouched: a privileged hostPID DaemonSet shipped as a manifest from this repo, or a standalone orphan-reaper.service systemd unit ordered After=k3s.service (separate unit, not a drop-in). Durable-state workloads (VictoriaMetrics, ClickHouse) need this; scratch-state workloads are covered by the init-wipe ticket instead.