Record M8.2 live verification, backlog and accepted default-project risk

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>
This commit is contained in:
dingo
2026-09-29 13:03:34 -04:00
co-authored by Claude Opus 5.5
parent df0c4f4efb
commit bd4128d55c
6 changed files with 62 additions and 4 deletions
+26
View File
@@ -2663,3 +2663,29 @@ Evidence:
- Not executed: applying anything to the cluster, the admission policy's CEL
compilation (it needs an API server; the runbook validates it with a server
dry run first), and `tools/ops/verify-isolation.sh`.
## M8.2 live verification - 2026-09-29
The maintainer applied the dev, stage and World0 platform overlays, the World0
admission policy and the stage and World0 AppProjects, then ran
`tools/ops/verify-isolation.sh` against the cluster. The output is kept locally in
`k8s-script-results.md`, which is gitignored.
- **Guardrails:** 24 PASS. All three namespaces have their labels (World0 is
protected), quota, limit range, default-deny and DNS policies, and three service
accounts.
- **RBAC negatives:** 144 PASS. None of the nine environment service accounts can
get or list secrets, create pods, delete PVCs or create rolebindings in any of the
three namespaces, and none can delete namespaces.
- **Admission:** 3 PASS, 2 SKIP. The policy is bound. Server dry runs deleting the
World0 namespace and a World0 service account were both denied, naming the
break-glass group. The secret and PVC cases were skipped because none exist in
World0 yet.
- **Cleanup:** 4 PASS. The tool refused `world0`, `evolution-world0`, `World0` and
the empty name.
- **Projects:** 3 FAIL, all a script defect. The project jsonpath concatenated the
destinations with the cluster whitelist, which prints `[]` when empty. The
destinations themselves were exactly `evolution-<env>`, with an empty whitelist.
The script now checks destinations and cluster kinds separately and accepts
`[]`. The corrected script has not been re-run on the cluster.
- **WARN:** the `default` AppProject allows every namespace. The maintainer
accepted this (docs/BACKLOG.md).