Restore an eligible deploy-monorepo Actions runner #684
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#684
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 deploy-eco-app workflow in coilyco-bridge/deploy fails before creating a job. Live cluster evidence shows the shared forgejo-runner-deploy StatefulSet at zero replicas. The healthy service-specific Eco runner registers label deploy but is scoped to coilyco-gaming/eco-app, so it cannot accept jobs from coilyco-bridge/deploy. This blocks rollout of the committed Eco App Tailscale sidecar removal.\n\nOperator completion:\n* Restore or define a runner eligible for coilyco-bridge/deploy using the existing runner precedent.\n* Re-dispatch deploy-eco-app.yml on main.\n* Verify the rollout succeeds and the coilysiren-eco-app app Deployment has only the application container.\n* Then complete the Terraform-owned Eco tailnet key and machine cleanup tracked in infrastructure issue 683.