chore(observability): delete Grafana live resources (manual followup to #388) #391
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#391
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 tracked-code Grafana teardown landed in #388 (merged as
15b0f98). This issue tracks the live-resource deletion, which needskubectl/terraformagainst kai-server's k3s and is Kai's manual followup - not a headless-agent task.Checklist
helm uninstall grafana -n observabilityobservabilitynamespace (the 2 GiB data volume).terraformapply inaws-inventoryto drop thegrafana.coilysiren.meRoute53 A record (the record was removed from tracked code in #388, the apply deletes the live record).grafana.coilysiren.me.terraform/grafanaremote state (the module dir was deleted in #388).Notes
Refs
Triage:
P3/interactive- Delete live Grafana resources; body states it is a manual destructive kubectl/terraform followup, not a headless task.(goose-style pass; claude as the judgment engine, applied 2026-06-23)
Closed in the 2026-08-26 backlog burn-down (coilyco-bridge/agentic-os-kai#901).
Closing as largely overtaken. #388 removed every tracked Grafana reference and #680 records the release already scaled to zero on kai-server. The residual PVC, DNS record, and remote-state cleanup belongs with #680's guarded retirement path rather than as its own issue.
This was
priority/P3, the default tier that unsure and unscored issues land in, so it had never been positively judged worth keeping. The 2026-08-26 burn-down ranked the whole P3 pool and cut the bottom. Closed here means not on the list, not wrong or worthless.If this is live work, reopen it. The whole set is recoverable with
state:closed label:burndown-2026-08.