cleanup: fully remove orphaned council-complaints app #9
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "wizard/council-cleanup"
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?
Full teardown of the abandoned council-complaints app (Islington civic-reporting pilot).
Live cluster (already done, out-of-band)
The app was already dead (deployments scaled 0/0, image only on the decommissioned
registry.viktorbarzin.mewhich 404s) and was never in Terraform, so its live resources were removed directly viakubectl(no TF to drift from):council-complaintsdeleted (cascaded deployments, worker, backup CronJob, service, 2 ingressescomplaints.viktorbarzin.me+complaints-admin.viktorbarzin.me, secrets, both PVCs).Retain-policy PVs (council-complaints-backup,council-complaints-uploads) deleted.192.168.1.127:/srv/nfs/council-complaints-final-backup/council-complaints-backup-20260621-133017.tgz(78 dump files, integrity-verified). The uploads PVC was empty (0 files).Repo references (this PR)
service-catalog.md: drop the council-complaints row.ci-cd.md+.claude/CLAUDE.md: drop it from the GHA->ghcr app list.require-trusted-registries: theregistry.viktorbarzin.me/*allowlist comment falsely claimed council-complaints as the last referencer; rewritten. The allowlist line itself is kept (registry-scoped, not app-specific; a stale completed wealthfolio-sync Job still carries that image ref).Deliberately NOT changed
The dated historical plan docs
docs/plans/2026-05-16-auto-upgrade-apps-{design,plan}.mdstill mention council-complaints inside a frozen "10 GHA-migrated repos (memory id=388)" snapshot. Left as-is so the point-in-time record stays accurate — editing would falsify the count/list.🤖 Generated with Claude Code
The council-complaints app (Islington civic-reporting pilot) has been abandoned. It was already dead in the cluster (deployments scaled 0/0, image only on the decommissioned registry.viktorbarzin.me which 404s), and it was never in Terraform — only docs + a kyverno comment referenced it. Its live cluster resources (namespace, both NFS-backed PVs, ingresses) were torn down out-of-band via kubectl (nothing in TF to drift from); the DB-dump PVC was backed up to NFS first. This removes the remaining repo references to the live app: - service-catalog.md: drop the council-complaints row - ci-cd.md + .claude/CLAUDE.md: drop it from the GHA->ghcr app list - kyverno require-trusted-registries: the registry.viktorbarzin.me/* allowlist comment claimed council-complaints as the last referencer; rewrite it (no live workload pulls from that registry now; only stale completed Job records still carry the ref). The allowlist line itself is kept (registry-scoped, not app-specific). Historical point-in-time plan docs (docs/plans/2026-05-16-auto-upgrade- apps-{design,plan}.md) still mention it inside a frozen "10 GHA-migrated repos (memory id=388)" snapshot; left as-is so the dated record stays accurate. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>