Part of #11804, step 4 (docs/OPERATING.md, "The vxrail without a control plane"). Nothing here moves onto the vxrail as a cluster service.
Done:
[ ] Forgejo: once no release reaches it (#8942) and outside pulls are sent to the forge (#8950), a final forgejo dump and a pg_dump of its CloudNativePG database go, encrypted, to the off-site bucket of #11805; trevato-apps/gitops is mirrored into the forge first (#8948). The dump's restore is tried once into a scratch Forgejo and the result recorded here.
[ ] Each tenant app's CloudNativePG database, on the owner's call per app (#8951's list): brought into the forge (Bring or Migrate; the app moves to SQLite under FORGE_APP_DATA, docs/APPS.md) or archived as an encrypted pg_dump in the off-site bucket. No CloudNativePG operator and no Postgres for them on the vxrail.
[ ] MinIO's contents are copied once to the off-site bucket.
Rollback per item: the dump restores where it came from while pg-grand runs; nothing is deleted on pg-grand by this issue.
Part of #11804, step 4 (docs/OPERATING.md, "The vxrail without a control plane"). Nothing here moves onto the vxrail as a cluster service.
Done:
forgejo dumpand apg_dumpof its CloudNativePG database go, encrypted, to the off-site bucket of #11805; trevato-apps/gitops is mirrored into the forge first (#8948). The dump's restore is tried once into a scratch Forgejo and the result recorded here.FORGE_APP_DATA, docs/APPS.md) or archived as an encryptedpg_dumpin the off-site bucket. No CloudNativePG operator and no Postgres for them on the vxrail.Rollback per item: the dump restores where it came from while pg-grand runs; nothing is deleted on pg-grand by this issue.
Files: docs/OPERATING.md, docs/PLATFORM.md