coulomb/activity-core
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
activity-core/k8s/backup-release
History
tegwick afa1058062
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details
Build and Publish Container Image / build-and-push (push) Successful in 42s
Details
Record repaired backup lane and stage bounded consumer refresh packet 
Assistant: codex
Assistant-Model: gpt-6.1-sol
Assistant-Session: 01a1029d-2c93-7500-a0e0-e3e089668b29
2026-10-03 21:58:57 +02:00
..
bundle.yaml Record repaired backup lane and stage bounded consumer refresh packet 2026-10-03 21:58:57 +02:00
README.md Record repaired backup lane and stage bounded consumer refresh packet 2026-10-03 21:58:57 +02:00
worker-patch.yaml Record repaired backup lane and stage bounded consumer refresh packet 2026-10-03 21:58:57 +02:00

README.md

Reviewed candidate backup client refresh

Prepared from railiance-platform source f1a780d830a118eecdc0ada1885e7b8f95b51072; immutable Forgejo ConfigMap backup-verified-debb9e4c59c9 and its existing mount patch are review artifacts. This directory is excluded from ordinary GitOps kustomization and has not been applied. It preserves existing env and other mounts.

Before runtime promotion:

  1. Repair repo-manager historical custodian-WP-* identifier compatibility without renumbering those owner records. Exact primary projection is currently unproved.
  2. Synchronize approved railiance-platform source on railiance01, so CNPG's existing hostPath receives the corrected public DAV header. This ConfigMap updates Forgejo only; it does not update CNPG.
  3. Confirm ESO's refreshed lane after KV4 publication, using safe metadata and privately compared credential equality if needed, never printed Secret bodies.
  4. Review the immutable bundle and scoped mount patch, then incorporate the new ConfigMap and volume reference into the adopted k8s/gitops source. Use reviewed ArgoCD sync rather than the old direct deployment patch helper. Keep the old immutable bundle until no rollback ReplicaSet references it.
  5. Verify worker recreation after source/ESO refresh, run python3 scripts/inspect_backup_delivery.py --platform-root ~/railiance-platform, and require both mounted source comparisons true. EnvFrom needs a new process; ESO Ready alone is insufficient.
  6. Obtain a separately reviewed existing bounded backup/provider receipt before declaring activity consumer acceptance. Do not automatically fire schedules.

No image update, worker restart, schedule or provider mutation has occurred. Current source-owned error-boundary hardening from T06 remains separate; this packet does not claim it was loaded by the existing image.