coulomb/reuse-surface
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Correct deploy guide for the Gitea registry retirement (REUSE-WP-0020-T05)
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details
ci / validate-registry (push) Successful in 2m44s
Details
Build and Publish Container Image / build-and-push (push) Successful in 49s
Details

Browse source 
The guide described gitea.coulomb.social as the live registry and its manual
build commands still pushed there. CoulombCore is switched off 2026-08-31.

Also record what the registry actually contains: authenticated tags/list shows
latest, main-bca7165, main-f9d957a and no e3ae22e — so the tag pinned in
railiance-apps/helm/reuse-surface-values.yaml cannot be pulled today, making
ImagePullBackOff a present risk on any restart rather than a future one.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
tegwick 2026-08-21 00:06:07 +02:00
parent 0c6b1e2538
commit b035664890
2 changed files with 50 additions and 20 deletions
Download patch file Download diff file Expand all files Collapse all files

30
workplans/REUSE-WP-0020-coulombcore-retirement-cutover.md
View file

@ -154,12 +154,32 @@ priority: high
Deadline-bound: must land before **2026-08-31**.
1. Verify which tags actually exist in
`forgejo.coulomb.social/coulomb/reuse-surface` (registry API needs auth;
anonymous `GET /v2/.../tags/list` returns `401`) and that
`.forgejo/workflows/image.yaml` is green on `main`.
1. ~~Verify which tags actually exist.~~ **Done 2026-08-20.** Authenticated
against the registry with the workstation's stored Forgejo credentials:
```
GET /v2/coulomb/reuse-surface/tags/list
→ {"tags": ["latest", "main-bca7165", "main-f9d957a"]}
```
**There is no `e3ae22e` tag.** The pinned manifest cannot pull today — this
is confirmed, not inferred. `main-f9d957a` (2026-07-08, REUSE-WP-0019-T06)
is the newest build; the 10 commits between it and HEAD were docs, workplans,
and licence changes that do not match the image workflow's path filters, so
no newer image exists yet.
2. Bump `image.tag` in `railiance-apps/helm/reuse-surface-values.yaml` from
`e3ae22e` to a verified Forgejo tag at current HEAD.
`e3ae22e` to a verified Forgejo tag.
**Prefer a build of current HEAD over `main-f9d957a`.** T02's compose
hardening is not in `main-f9d957a`, and without it re-enabling
`evidence-binder` (T04) would take production to HTTP 500 again. Pushing
HEAD touches `reuse_surface/**`, so CI will produce `main-<short-sha>`;
deploy that tag. Not pushed yet — pushing to the shared remote needs an
explicit go-ahead.
Left deliberately unmodified for now: writing a tag that has not been built
is worse than leaving the current wrong one, since it converts a latent
failure into an immediate one on the next reconcile.
3. Correct `docs/deploy/reuse-kubernetes.md`, which still describes Gitea as
the live registry and its manual `docker build`/`push` commands still
target `gitea.coulomb.social`.