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>
This commit is contained in:
@@ -2781,3 +2781,33 @@ admission policy and the stage and World0 AppProjects, then ran
|
||||
- The digests the maintainer pasted are local image IDs from the build step, not
|
||||
registry digests. The registry digest is printed by the Publish step.
|
||||
- Not executed: bootstrapping the platform Application, or any Argo sync.
|
||||
|
||||
## M8.4 region host - 2026-09-29
|
||||
|
||||
- Windows MSVC Release CTest 59/59, including the new opening code.
|
||||
`lineage-region-contracts` proves `development_opening(7)` is byte-identical
|
||||
to the fixture, and that world 100 differs only by identity.
|
||||
- WSL Linux `checks` set: 59/59 in each configuration. The format check passed.
|
||||
- PostgreSQL suites: Release, analysis and ASan/UBSan passed. Analysis passed after
|
||||
one optional-access fix in `provision`.
|
||||
- Provisioning test:
|
||||
- A runtime login cannot provision.
|
||||
- The owner provisions `world=7 region=86 sequence=0 tick=0`, and a rerun reports
|
||||
`already-provisioned`.
|
||||
- A server then became ready and acknowledged ticks 1–5, after which the tool
|
||||
reported `sequence=1 tick=5` and left the region untouched.
|
||||
- Mutation: removing the already-provisioned early return was caught.
|
||||
- `deploy-policy-check.py`: 50 objects, 0 failures. Four new mutations were each
|
||||
caught:
|
||||
- a build identity differing from the image digest;
|
||||
- a RollingUpdate strategy;
|
||||
- a CPU limit;
|
||||
- a grace period shorter than the drain.
|
||||
The checker first misread overlay patches as whole Deployments; it now checks
|
||||
only the base.
|
||||
- Kustomize renders dev and stage in order: egress policy (−2), migration hook
|
||||
(−1), provisioning hook (0), Deployment and Service (1), then the store check
|
||||
(PostSync).
|
||||
- `region-drill.sh` passed `bash -n`, and refuses World0 before kubectl (also
|
||||
enforced by the policy check).
|
||||
- Not executed: the in-cluster region sync and the drill.
|
||||
|
||||
Reference in New Issue
Block a user