Server 3e5b8cef and postgres-tools ceb7ea27, both from CI run 388 (bda1631). The
client job passed after a rerun; the first attempt hit a one-off Xvfb window-open
failure. The server image now contains evo-grant-broker, and region/dev enables
the grant-broker-dev component. Build 4a8b0a9d, which committed region 4 history,
stays retained.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Server 4a8b0a9d from CI run 380 (7c16a13). Build 58aab8aa, which committed region 4
history, stays retained. Also fixes a literal newline in the v10 schema doc.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Server 58aab8aa from CI run 378 (1675bb6) lets DEV cellular sessions use the
4-hour grant ceiling. Region 4's genesis build e891f942 stays retained so the
region recovers under the new image.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Promotes server e891f942 and postgres-tools fe3558e9 (schema v38) from CI run 376
and moves the DEV region host and provision job to region 100/4 with the
cellular-v4 opening (rules 5): engulfment, detritus, budding wildlife, permadeath
and offline freeze. Regions 1-3 stay in the stores untouched. Recorded in
ADR-0123, the M11.9 plan and the validation log.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The cellular-v1 provision hook failed with PublicationError::rejected:
the dev store Jobs still pinned the schema-v11 postgres-tools image,
so PostgreSQL refused the profile-4 genesis manifest. Pin the
postgres-tools image from Gitea run 350 (source ae3b2b4, migrations
through 0033), the same run that built the promoted dev server image.
Also refresh the dev session window (3 h).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Online, snapshot-consistent bundles (pg_dump at an exported snapshot, immutable
objects verified by digest, MANIFEST of versions/builds/heads, SHA256SUMS); a
fail-closed restore that audits every region's full history on independent
storage; an isolated rebuild through clones that serves under load; an
operator-run in-cluster backup streamed off the cluster. backup-check.sh runs in
every PostgreSQL build, with corruption, missing-object, tampered-manifest and
non-empty-target refusals. Destination, encryption, schedule and WAL archiving
remain on the backlog.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
At the maintainer's request everything but Secrets and the store node
label now goes through Argo CD. aevolution-platform syncs one bundle
(World0 admission policy, Retain storage class, each environment's
namespace, guardrails, service accounts and object claim) with
self-heal, no prune and Prune=false,Delete=false on every object; the
admission policy also protects the platform app and project. Store Jobs
become kustomize components used as PreSync (migrate) and PostSync
(check-store) hooks per environment, and the policy check refuses any
unresolved marker in a path an Application syncs.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The maintainer's login Secrets carry pg_service.conf ([evolution]),
pgpass and ca.crt. Add a strict read_pg_service (known keys only,
verify-full unless a local socket, bounded size) behind --pg-service in
evo-server and evo-world-clone, mount each login Secret whole in the
store Jobs instead of reading aevolution-db, and fix the migrate Job's
PGSERVICE to the [evolution] section. Record the store node choice,
per-environment databases and the backup plan.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Keep the filesystem object store on a node-local Retain-class PVC per
environment (ADR-0070), with the database on the external PostgreSQL VM.
Because local-path does not enforce sizes, the object store now refuses
new objects below a free-space reserve with a distinct full error, so a
full volume publishes and acknowledges nothing. evo-world-clone gains
check-store to qualify volume retention, reserve, database version/TLS
and the runtime privilege boundary from inside the cluster; it now ships
in the server image. Add the storage class, object claims, hand-applied
store Jobs, policy rules forbidding password env vars, and the runbook.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>