Remove capacitor-dev namespace from cluster (3 alerts) #115

Closed
opened 2026-03-18 17:04:21 +00:00 by forgejo_admin · 3 comments

Lineage

plan-pal-e-platform → Platform Hardening → noise reduction

Repo

forgejo_admin/pal-e-deployments (kustomize overlay cleanup)

User Story

As a platform operator
I want capacitor-dev removed from the cluster
So that 3 crash-loop alerts stop firing (483 restarts in 36h)

Context

Stale dev namespace with nginx proxy crash-looping (502 on every liveness probe). Biggest source of alert noise — generating CrashLooping, RestartStorm, and ReplicasMismatch alerts continuously. No persistent data. Not managed by ArgoCD or Terraform.

Kustomize overlay exists at ~/pal-e-deployments/overlays/capacitor-dev/prod/ (4 files). Tailscale funnel at capacitor-dev.tail5b443a.ts.net.

File Targets

  • ~/pal-e-deployments/overlays/capacitor-dev/ — delete entire directory, commit and push

Files NOT to touch:

  • terraform/ — no Terraform config for capacitor-dev
  • Other kustomize overlays

Acceptance Criteria

  • Namespace capacitor-dev does not exist
  • Tailscale device capacitor-dev removed from tailnet
  • Kustomize overlay removed from pal-e-deployments
  • All 3 alerts clear (CrashLooping, RestartStorm, ReplicasMismatch)

Test Expectations

  • kubectl get ns capacitor-dev returns NotFound
  • ls ~/pal-e-deployments/overlays/capacitor-dev/ returns not found
  • AlertManager shows no capacitor-dev alerts

Constraints

  • No data at risk — stateless
  • Close Issue #101 (deploy capacitor dev hub) as superseded
  • Tailscale operator auto-cleans funnel device when ingress is deleted

Checklist

  • kubectl delete namespace capacitor-dev
  • Kustomize overlay removed + committed
  • Issue #101 closed
  • Alerts clear
  • pal-e-platform — project board
  • Issue #101 — deploy capacitor dev hub (superseded)
  • Issue #109 — umbrella alert cleanup
### Lineage `plan-pal-e-platform` → Platform Hardening → noise reduction ### Repo `forgejo_admin/pal-e-deployments` (kustomize overlay cleanup) ### User Story As a platform operator I want capacitor-dev removed from the cluster So that 3 crash-loop alerts stop firing (483 restarts in 36h) ### Context Stale dev namespace with nginx proxy crash-looping (502 on every liveness probe). Biggest source of alert noise — generating CrashLooping, RestartStorm, and ReplicasMismatch alerts continuously. No persistent data. Not managed by ArgoCD or Terraform. Kustomize overlay exists at `~/pal-e-deployments/overlays/capacitor-dev/prod/` (4 files). Tailscale funnel at `capacitor-dev.tail5b443a.ts.net`. ### File Targets - `~/pal-e-deployments/overlays/capacitor-dev/` — delete entire directory, commit and push Files NOT to touch: - `terraform/` — no Terraform config for capacitor-dev - Other kustomize overlays ### Acceptance Criteria - [ ] Namespace `capacitor-dev` does not exist - [ ] Tailscale device `capacitor-dev` removed from tailnet - [ ] Kustomize overlay removed from pal-e-deployments - [ ] All 3 alerts clear (CrashLooping, RestartStorm, ReplicasMismatch) ### Test Expectations - [ ] `kubectl get ns capacitor-dev` returns NotFound - [ ] `ls ~/pal-e-deployments/overlays/capacitor-dev/` returns not found - [ ] AlertManager shows no capacitor-dev alerts ### Constraints - No data at risk — stateless - Close Issue #101 (deploy capacitor dev hub) as superseded - Tailscale operator auto-cleans funnel device when ingress is deleted ### Checklist - [ ] `kubectl delete namespace capacitor-dev` - [ ] Kustomize overlay removed + committed - [ ] Issue #101 closed - [ ] Alerts clear ### Related - `pal-e-platform` — project board - Issue #101 — deploy capacitor dev hub (superseded) - Issue #109 — umbrella alert cleanup
Author
Owner

Scope Review: READY

Review note: review-194-2026-03-18
Scope is solid — all 10 template sections present, file targets verified (5 files in overlay directory), zero capacitor-dev references outside the overlay itself. No blocking dependencies, acceptance criteria are all agent-verifiable. Ready for dispatch.

## Scope Review: READY Review note: `review-194-2026-03-18` Scope is solid — all 10 template sections present, file targets verified (5 files in overlay directory), zero capacitor-dev references outside the overlay itself. No blocking dependencies, acceptance criteria are all agent-verifiable. Ready for dispatch.
Author
Owner

Scope Review: READY

Review note: review-194-2026-03-18
Scope is solid — all file targets verified, acceptance criteria are testable, no blocking dependencies. Minor cosmetic: context says "4 files" but overlay has 5 (kustomization.yaml uncounted); File Targets correctly says "delete entire directory" so no impact.

## Scope Review: READY Review note: `review-194-2026-03-18` Scope is solid — all file targets verified, acceptance criteria are testable, no blocking dependencies. Minor cosmetic: context says "4 files" but overlay has 5 (kustomization.yaml uncounted); File Targets correctly says "delete entire directory" so no impact.
Author
Owner

Both parts complete:

Part 1 -- kubectl cleanup:

  • kubectl delete namespace capacitor-dev -- done. Namespace was in CrashLoopBackOff with 514 restarts.
  • Verified: kubectl get ns capacitor-dev returns NotFound.

Part 2 -- kustomize overlay removal:

  • pal-e-deployments PR #32 (merged) removed overlays/capacitor-dev/.

Related cleanup:

  • Issue #101 (Deploy Capacitor dev hub) closed as superseded -- the SPA path-proxying approach was abandoned.
Both parts complete: **Part 1 -- kubectl cleanup:** - `kubectl delete namespace capacitor-dev` -- done. Namespace was in CrashLoopBackOff with 514 restarts. - Verified: `kubectl get ns capacitor-dev` returns NotFound. **Part 2 -- kustomize overlay removal:** - pal-e-deployments PR #32 (merged) removed `overlays/capacitor-dev/`. **Related cleanup:** - Issue #101 (Deploy Capacitor dev hub) closed as superseded -- the SPA path-proxying approach was abandoned.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
forgejo_admin/pal-e-platform#115
No description provided.