Keep the kai-server image-build runner disabled after disk pressure #705
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#705
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?
The 2026-07-31 recurrence showed kai-server rising from 76.3% to about 84% root use while the scoped Flight Deck image-build runner resumed dev-base publication after mass eviction. Live scale-to-zero was reverted by Flux. Track replicas zero in the scoped overlay, retain the runner claims for rollback, update the feature inventory and runner walkthrough, and verify Flux converges the StatefulSet to 0/0 while ordinary CI and services remain healthy. Root-cause capacity work stays in #624 and migration stays in #693.