Deprovision eco-mcp-app (deprecated) #41

New issue

Open

opened 2026-07-03 05:33:22 +00:00 by coilysiren · 0 comments

coilysiren commented

2026-07-03 05:33:22 +00:00

Owner

eco-mcp-app is deprecated (confirmed by Kai). It is currently half-retired: eco-mcp.coilysiren.me returns 503 "no available server" (no healthy pod), but the ingress, DNS, and supporting cloud resources still exist and still serve errors to any visitor. Deprovision it cleanly.

Teardown checklist

k8s resources in namespace coilysiren-eco-mcp-app: Deployment, Service, Ingress, ExternalSecrets, then the namespace itself.
DNS / ingress host eco-mcp.coilysiren.me.
Tailscale federated identity for eco-mcp (it is in the terraform tailscale-merge list).
terraform aws-inventory entry (eco-mcp = 300).
SSM params used only by eco-mcp (its Eco admin token). Confirm the FRED key is not shared before removing it.
GHCR / package image (ghcr.io/.../eco-mcp-app).
CI build-and-publish workflow (moot once the repo is archived).
Repo already archived on the forge (coilyco-flight-deck/eco-mcp-app) - confirm.

Blocker - coordinate before deleting the code

eco-jobs-tracker git-imports eco-mcp-app for its embedded live server-status card (it "imports directly from sibling eco-mcp-app"). Deleting the eco-mcp code/repo breaks that card. Before retiring the code, either:

fold the server-status card into eco-app / the merged site (the DLT epic eco-app#37 does exactly this consolidation), or
vendor the card so jobs-tracker keeps rendering it.

The service teardown (k8s / DNS / secrets / image) can proceed independently - just do not delete the repo or the git dep until the card has a new home.

Note on who does this

This is a destructive infra action (deleting k8s + DNS + secrets) and needs host creds this read-only director surface does not have. So it is a dispatched run or a hands-on teardown, not something to run from here.

eco-app#37 (DLT epic - the card's new home)
eco-ops#25 (once gone, drop eco-mcp from any uptime probe so it stops alerting)

eco-mcp-app is **deprecated** (confirmed by Kai). It is currently half-retired: `eco-mcp.coilysiren.me` returns 503 "no available server" (no healthy pod), but the ingress, DNS, and supporting cloud resources still exist and still serve errors to any visitor. Deprovision it cleanly. ## Teardown checklist - [ ] k8s resources in namespace `coilysiren-eco-mcp-app`: Deployment, Service, Ingress, ExternalSecrets, then the namespace itself. - [ ] DNS / ingress host `eco-mcp.coilysiren.me`. - [ ] Tailscale federated identity for `eco-mcp` (it is in the terraform tailscale-merge list). - [ ] terraform aws-inventory entry (`eco-mcp = 300`). - [ ] SSM params used only by eco-mcp (its Eco admin token). **Confirm the FRED key is not shared** before removing it. - [ ] GHCR / package image (`ghcr.io/.../eco-mcp-app`). - [ ] CI build-and-publish workflow (moot once the repo is archived). - [ ] Repo already archived on the forge (`coilyco-flight-deck/eco-mcp-app`) - confirm. ## Blocker - coordinate before deleting the code **eco-jobs-tracker git-imports eco-mcp-app** for its embedded live server-status card (it "imports directly from sibling eco-mcp-app"). Deleting the eco-mcp code/repo breaks that card. Before retiring the code, either: - fold the server-status card into eco-app / the merged site (the DLT epic eco-app#37 does exactly this consolidation), or - vendor the card so jobs-tracker keeps rendering it. The **service** teardown (k8s / DNS / secrets / image) can proceed independently - just do not delete the repo or the git dep until the card has a new home. ## Note on who does this This is a destructive infra action (deleting k8s + DNS + secrets) and needs host creds this read-only director surface does not have. So it is a dispatched run or a hands-on teardown, not something to run from here. ## Related - eco-app#37 (DLT epic - the card's new home) - eco-ops#25 (once gone, drop eco-mcp from any uptime probe so it stops alerting)

coilysiren added the

label

2026-07-03 05:33:22 +00:00

coilysiren changed title from ~~eco-mcp-app is down (503 'no available server')~~ to Deprovision eco-mcp-app (deprecated)

2026-07-03 05:38:44 +00:00

coilysiren referenced this issue from coilyco-flight-deck/ward

2026-07-05 05:17:19 +00:00

Context-repo hydration: WARD_CONTEXT_REPOS=StrangeLoopGames/Eco is declared but never present, so mod runs can't verify against Eco source #611

coilysiren referenced this issue

2026-07-05 06:47:05 +00:00

P1: prod deploy frozen since #60 — publish gates on the always-failing mods job (app image has no mods). Decouple + fix the mods gate #68