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

Add failure-safe cluster image capture hook
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 2s
Details

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a06ecb-456a-71c2-b41e-0755d336e883
This commit is contained in:
codex 2026-09-05 10:04:38 +02:00
parent 05f315be84
commit da42f764c0
4 changed files with 60 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

10
docs/forgejo-package-prune.md
View file

@ -106,8 +106,14 @@ Migration and rollout sequence:
other clusters' prior entries during outages. Run the hook on the durable
host, or transfer the complete export there before invoking it.
The publisher is implemented here; host migration and the activity-core mount
and rollout-hook adoption are tracked in `RPF-WP-0028` until verified live.
`tools/cmd/refresh-live-images` captures regular, init and ephemeral container
images with a bounded kubectl call and publishes only after all requested
contexts succeed. `CONTEXTS` selects contexts; `EXTRA_LIVE_FILES` supplies saved
exports. Bare image names are accepted. Failed captures preserve the inventory.
The host installation exposes `~/.local/bin/railiance-live-images-refresh`;
invoke it after cluster image rollouts. Activity-core's `make refresh-live-images`
delegates to the same implementation. Live installation evidence is tracked in
`RPF-WP-0028`.
## Rollback procedure