Delete the retired coilysiren-backend image repository from the standalone registry #655

New issue

Open

opened 2026-07-27 06:52:48 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-07-27 06:52:48 +00:00

Member

Outcome

Delete the retired coilysiren-backend image repository from the standalone kai-server registry after the live workload and rollback gates prove that no consumer needs it.

This issue deletes one image repository. It does not delete the standalone registry, its PVC, the backend database, or the backend namespace.

Target

Standalone-registry repository: coilysiren-backend
Product disposition: deprecated
Archived source: https://github.com/coilyco-flight-deck/backend
Deploy-source retirement: coilyco-bridge/deploy@6ae879e147

Preconditions

Ops completes the live backend workload and data-retention decision in coilysiren/inbox#277.
A controller and running-pod inventory returns zero references to coilysiren-backend in the standalone registry.
Ops records the current tag and manifest inventory plus the retain-or-discard decision for rollback images.
Ops confirms whether the registry backup must survive through a named rollback window.

Operator scope

Inventory every tag and manifest under coilysiren-backend without exposing credentials.
Stop if any active controller, pod, job, or rollback procedure still references the image.
Record the approved discard or retained-backup disposition.
Delete the repository manifests from the standalone registry.
Run blob garbage collection only through the established whole-registry retirement procedure, preserving blobs referenced by other repositories.
Return before-and-after catalog evidence and confirm unrelated repositories remain readable.

Acceptance

The issue records the pre-delete tag and manifest inventory.
Live controller and running-pod evidence shows zero backend image consumers.
The rollback and backup retention decision is explicit.
The standalone registry catalog no longer lists coilysiren-backend.
Exact tag and manifest lookups for the retired image return not found.
Other retained registry repositories remain readable.
infrastructure#653 links the evidence and treats the backend catalog entry as deleted.

Registry migration and retirement gates: #653
Backend live workload and data disposition: coilysiren/inbox#277
Program authority: coilysiren/inbox#276

Codex, via engineer surface

## Outcome Delete the retired `coilysiren-backend` image repository from the standalone kai-server registry after the live workload and rollback gates prove that no consumer needs it. This issue deletes one image repository. It does not delete the standalone registry, its PVC, the backend database, or the backend namespace. ## Target * Standalone-registry repository: `coilysiren-backend` * Product disposition: deprecated * Archived source: https://github.com/coilyco-flight-deck/backend * Deploy-source retirement: https://forgejo.coilysiren.me/coilyco-bridge/deploy/commit/6ae879e147a51052b7715520b024a47058fd44d8 ## Preconditions * Ops completes the live backend workload and data-retention decision in https://forgejo.coilysiren.me/coilysiren/inbox/issues/277. * A controller and running-pod inventory returns zero references to `coilysiren-backend` in the standalone registry. * Ops records the current tag and manifest inventory plus the retain-or-discard decision for rollback images. * Ops confirms whether the registry backup must survive through a named rollback window. ## Operator scope 1. Inventory every tag and manifest under `coilysiren-backend` without exposing credentials. 2. Stop if any active controller, pod, job, or rollback procedure still references the image. 3. Record the approved discard or retained-backup disposition. 4. Delete the repository manifests from the standalone registry. 5. Run blob garbage collection only through the established whole-registry retirement procedure, preserving blobs referenced by other repositories. 6. Return before-and-after catalog evidence and confirm unrelated repositories remain readable. ## Acceptance * [ ] The issue records the pre-delete tag and manifest inventory. * [ ] Live controller and running-pod evidence shows zero backend image consumers. * [ ] The rollback and backup retention decision is explicit. * [ ] The standalone registry catalog no longer lists `coilysiren-backend`. * [ ] Exact tag and manifest lookups for the retired image return not found. * [ ] Other retained registry repositories remain readable. * [ ] infrastructure#653 links the evidence and treats the backend catalog entry as deleted. ## Related * Registry migration and retirement gates: https://forgejo.coilysiren.me/coilyco-flight-deck/infrastructure/issues/653 * Backend live workload and data disposition: https://forgejo.coilysiren.me/coilysiren/inbox/issues/277 * Program authority: https://forgejo.coilysiren.me/coilysiren/inbox/issues/276  Codex, via engineer surface

coilyco-ops added the

autonomy

live-collab

label

2026-07-27 06:52:49 +00:00

coilyco-ops referenced this issue

2026-07-27 06:52:49 +00:00

Migrate the standalone k3s image registry inventory to Forgejo OCI #653

coilyco-ops added the

priority

label

2026-07-29 03:46:31 +00:00