--upgrade-plan: what --upgrade-store would do, read only #457

Merged
jcoffey-dev merged 1 commits from feat/upgrade-plan into main 2026-11-18 21:01:21 +00:00
1 Commits
Author SHA1 Message Date
jcoffey-dev 9f3aa90127 --upgrade-plan: what --upgrade-store would do, read only
ci / fork-checks (pull_request) Skipped
ci / build (pull_request) Skipped
github/ci (branch) GitHub Actions
ci / github (pull_request) Successful in 13m46s
For the Helm chart's upgrade hook (K-C9). The 2026.x to 27.1 crossing has
a layout step that isn't rolling-safe: a rolling update stalls, because
the new pod waits for the old ones to stop. The hook has to stop every
server pod first, but only when a step needs it, which the server knows
and the chart shouldn't hard-code (S5).

inbuxa --upgrade-plan boots as --upgrade-store does, writes nothing, and
prints one line of JSON: the store's layout version, this build's, and
each step with whether it's rolling-safe. Its exit code is for a shell
to branch on: 0 nothing to do, 3 rolling-safe steps only, 4 a step needs
every other node stopped, 2 a newer release changed the store, 1 can't
tell.

The store_version integration test covers a current store, layout 1 and
2, and a newer store, and that the plan leaves the mark alone.
2026-11-18 13:45:25 -07:00