2 Commits
Author SHA1 Message Date
dingoandClaude Opus 5.5 4921231311 deploy(argocd): let the dev project carry ConfigMaps
Foundation / checks (checks) (push) Successful in 4s
Foundation / checks (client) (push) Successful in 4s
Foundation / checks (ecs) (push) Successful in 4s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (postgres) (push) Successful in 5s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 4m27s
Foundation / postgres-tools (push) Successful in 5s
Foundation / image (push) Successful in 4s
Foundation / server-image (push) Successful in 4s
The rules-12 tuning file reaches the provision Job as a kustomize-generated
ConfigMap, which the dev AppProject refused ("ConfigMap is not permitted in
project aevolution-dev"), so the region-10 sync failed validation and applied
nothing. ConfigMaps carry only Git-managed, non-secret configuration; stage and
world0 projects already allow them. Projects are applied by hand.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-21 18:55:33 -04:00
dingoandClaude Opus 5.5 8ef69fab1d Add M8.4 region host deployment, provisioning hook and drill
Deploy evo-region per environment (ADR-0071): one replica with the
Recreate strategy (a rolling update would deadlock on the lease),
/readyz readiness, /livez liveness, no CPU limit and a drain inside the
grace period, with the image digest doubling as the build identity. A
new idempotent evo-world-clone provision subcommand creates genesis from
development_opening (byte-identical to the qualification fixture) as a
Sync hook after the migration. Dev and stage paths include their region;
a dev AppProject allows Deployment and Service; region-drill.sh times
rollout and forced-deletion recovery; the policy check enforces the
host's invariants.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-29 21:32:56 -04:00