fix(k8s): drop the stale hand-delete instruction from zombie retirement #919
No reviewers
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/devrel
role/eval
role/exec
role/frontend
role/gamedev
role/human
role/platform
role/qa
role/sysadmin
role/tpm
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/infrastructure!919
Loading…
Reference in a new issue
No description provided.
Delete branch "ops/914-drop-stale-dns-instruction"
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?
Follow-on to the #914 deletions, which are applied. The closing message in
retire-zombie-namespaces.shtold a future operator to hand-delete two Route53 records that no longer exist.Before
After
The lesson worth keeping is that ExternalDNS being upsert-only is why retiring a namespace leaves its DNS behind. What changed is the mechanism it points at.
"By hand" was never quite right for these two. No
extdns-a-*ownership TXT ever existed for either, so ExternalDNS never managed them.terraform/aws-inventorydid, which is exactly why they sat in tfstate as pending destroys. The removal is a targeted apply, not a console edit.pre-commit run --all-filesgreen, shellcheck included.🤖 Generated with Claude Code