Public: anyone can read this; the crew can change it.

Spin down the Kubernetes platform: everything lives in the forge #8953

Merged opened this in answer to

Check · Review · Land · Live done — Landed and live in production.

Merged

This pull adds the inventory for #7667 as `docs/PLATFORM.md`, linked from the README index. It changes no behaviour, and nothing is turned off or removed.

shipped production is serving it deploy 84c60a0

opened this

This pull adds the inventory for #7667 as docs/PLATFORM.md, linked from the README index. It changes no behaviour, and nothing is turned off or removed.

What changed

  • Inventory: the file has 11 rows. Each says what the forge or its apps take from the platform, what replaces it, what is already done, and the issue for the next step. The rows are:

- image build and registry - gitops and reconcile - pod and supervisor - ingress and TLS - identity - backup lanes (including the 36 GB forgejo-dump) - the Forgejo mirror where outsiders send pulls - hosted apps - the droplet release tick - the non-release Forgejo Actions jobs - previews of the forge's own repository

  • What #1432 retired: it states what #1432 delivered: checkout, preflight, swap, verify and swap-back, all on main. It also states what it did not retire:

- Production is not on FORGE_RELEASE_KEEPER=swap, and no dark-second figure from a child forge has been measured. - The Forgejo image, registry and chart path is still in the tree. - Release ticks still exist on the droplet and the Mac.

  • Gate and outside agents: the page describes the spin-down gate: a quiet period measured from access logs, a restore drill that does not touch the platform, a final snapshot, and the owner's go. It also records that the trevato-apps/forge route closes only after #6359 and #8935.
  • Tests: test/platform-doc.test.ts fails if a file the page names goes missing, or if the page drops a dependency or the "without the owner present" line. bun scripts/gate.ts and bun x tsc --noEmit are clean. test/platform-doc.test.ts and test/readme-front-door.test.ts pass.

Issues filed: #8940–#8952 are filed and linked on the map, one per next step. #7667 waits on #8952, and #8952 waits on every other step. One bug I found and fixed: #8940 had a placeholder body, which I replaced with the real drill and done-when.

Left alone

  • Unread parts: I could not read the gitops repository, the cluster's app list, or the droplet's tick from here, so the page marks them unread. #8948 and #8951 fill them in.
  • Stray issue: #8939 is a stray test issue titled "x" that I filed, and my token can't close it. Please close it.
  • Cuts and drills: I started no cut and ran no drill; each waits for the owner.

To try it: read docs/PLATFORM.md, then run bun test test/platform-doc.test.ts.

Closes #7667

commented

This pull adds the inventory for #7667 as docs/PLATFORM.md, linked from the README index. It changes no behaviour, and nothing is turned off or removed.

What changed

  • Inventory: the file has 11 rows. Each says what the forge or its apps take from the platform, what replaces it, what is already done, and the issue for the next step. The rows are:

- image build and registry - gitops and reconcile - pod and supervisor - ingress and TLS - identity - backup lanes (including the 36 GB forgejo-dump) - the Forgejo mirror where outsiders send pulls - hosted apps - the droplet release tick - the non-release Forgejo Actions jobs - previews of the forge's own repository

  • What #1432 retired: it states what #1432 delivered: checkout, preflight, swap, verify and swap-back, all on main. It also states what it did not retire:

- Production is not on FORGE_RELEASE_KEEPER=swap, and no dark-second figure from a child forge has been measured. - The Forgejo image, registry and chart path is still in the tree. - Release ticks still exist on the droplet and the Mac.

  • Gate and outside agents: the page describes the spin-down gate: a quiet period measured from access logs, a restore drill that does not touch the platform, a final snapshot, and the owner's go. It also records that the trevato-apps/forge route closes only after #6359 and #8935.
  • Tests: test/platform-doc.test.ts fails if a file the page names goes missing, or if the page drops a dependency or the "without the owner present" line. bun scripts/gate.ts and bun x tsc --noEmit are clean. test/platform-doc.test.ts and test/readme-front-door.test.ts pass.

Issues filed: #8940–#8952 are filed and linked on the map, one per next step. #7667 waits on #8952, and #8952 waits on every other step. One bug I found and fixed: #8940 had a placeholder body, which I replaced with the real drill and done-when.

Left alone

  • Unread parts: I could not read the gitops repository, the cluster's app list, or the droplet's tick from here, so the page marks them unread. #8948 and #8951 fill them in.
  • Stray issue: #8939 is a stray test issue titled "x" that I filed, and my token can't close it. Please close it.
  • Cuts and drills: I started no cut and ran no drill; each waits for the owner.

To try it: read docs/PLATFORM.md, then run bun test test/platform-doc.test.ts.

Approved

Docs-only: docs/PLATFORM.md, one README index line, and a test that the named files exist and the topics and the "without the owner present" line stay. No behaviour, no dependency, no code door to gate, so the security and both-doors items do not apply. The README change is an index link only, not a how-to. It is honest about what it could not read (marked unread) and about what #1432 did and did not retire. It is not pipeline work, but it is small, single-purpose and changes nothing the pipeline touches.

Two things I would do next: (1) post the inventory table on issue #7667 itself, or link it there, since box 1 says the inventory lists on the issue; (2) land #8948 and #8951 to turn the unread rows into read ones, and keep the test checking those rows once they are filled in.

Boxes 2-4 are plans filed as issues (#8940-#8952), not done, so they stay open.

commented

Left #7667 open: 3 unticked items remain (Outside agents work against the forge and are pointed there. The trevato-apps/forge route closes, once #6359 gives them a way in.; Each dependency is cut one at a time with a tested rollback. The forge is never dark without the owner's go.; The platform spins down only after a set period with nothing reaching it, measured from its access logs, and after a restore drill that does not touch it.).

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs