The maintainer applied the platform layer, World0 admission policy and projects; verify-isolation.sh passed every guardrail, RBAC-negative, admission dry-run and cleanup check. Its three project failures were a script defect (destinations and the empty cluster whitelist were printed together as "[]"); check them separately. Ignore local result files, add docs/BACKLOG.md with break-glass membership and the storage re-probe, and record leaving Argo's default project unrestricted as an accepted risk. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
3.7 KiB
AEvolution environments (M8.2)
The decision is recorded in ADR-0069. This runbook applies the platform layer, creates the per-environment references, and verifies isolation. Every step is manual, and none is performed by Argo CD.
Environments
| dev | stage | world0 | |
|---|---|---|---|
| Namespace | evolution-dev (exists) |
evolution-stage |
evolution-world0 |
| Purpose | Development | Clone, migration and soak rehearsal | Persistent world (launch gated by M8.8) |
| Protected by admission | No | No | Yes |
| Cleanup tool | Allowed | Allowed | Refused |
| AppProject / Application | aevolution-dev (live, manual) |
deploy/argocd/stage/*.example |
deploy/argocd/world0/*.example (deny window) |
| Database | Its own database and logins on the AEvolution PostgreSQL VM | Its own | Its own |
| World IDs | Development range | Clone targets (ADR-0067) | World0's own; never reused elsewhere |
Secret references (created by an operator, never committed)
Each namespace gets its own Secrets, with environment-specific values:
harbor-pull: a pull-only Harbor robot (docker-registry type).evolution-postgres-migrator: the migrator/owner login for that environment's database.evolution-postgres-runtime: the runtime login, a member of that environment's NOLOGIN runtime group (ADR-0060).aevolution-db: connection settings (host, address, port, database, TLS mode and root certificate). Mount it as files. The adapter reads a password file, neverPGPASSWORD.
A World0 credential must never exist in the dev or stage namespaces, and no dev or stage credential may reach the World0 database. Rotate by replacing the Secret and restarting the consumer.
Apply (cluster administrator)
# 1. Platform guardrails, per environment (dev adds labels, quota and policies to
# the existing namespace; its completed proof Job already complies).
kubectl apply -k deploy/kubernetes/platform/dev
kubectl apply -k deploy/kubernetes/platform/stage
kubectl apply -k deploy/kubernetes/platform/world0 # an empty, protected namespace
# 2. World0 admission protection (validate first, then apply).
kubectl apply --dry-run=server -f deploy/kubernetes/platform/admission/
kubectl apply -f deploy/kubernetes/platform/admission/
# 3. Projects (resolve the Application paths only when M8.4 adds workloads).
kubectl apply -f deploy/argocd/stage/project.yaml.example
kubectl apply -f deploy/argocd/world0/project.yaml.example
# 4. Verify: reads, can-i and server dry runs only.
bash tools/ops/verify-isolation.sh
Create the Secrets listed above in each namespace before any workload syncs.
Break-glass
How membership is granted is not decided yet; see docs/BACKLOG.md. Until it is, nobody holds the group, so World0 deletions are impossible short of removing the policy.
To delete World0 data or identity on purpose:
- Record the operation and its approval.
- Use a credential whose groups include
aevolution:world0-break-glass, for example a short-lived client certificate with that organization. - Take and verify a backup first (M8.7).
Removing the admission policy itself is the break-glass of last resort. It needs cluster-admin and must be recorded the same way. Never test by deleting World0: the verify script uses server-side dry runs.
Residual risks
defaultAppProject. It still allows every destination, so its applications (other projects, two with automated prune) can create objects in AEvolution namespaces. Admission denies only World0 deletions. The maintainer accepted this risk on 2026-09-29 and is leavingdefaultas it is (docs/BACKLOG.md).- World0 volumes.
local-pathprovisions volumes with Delete. Patch each World0 PV toRetainwhen it is bound, and the policy then keeps it there. Volumes stay node-local until M8.3.