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:
@@ -0,0 +1,16 @@
|
||||
# Backlog
|
||||
|
||||
These items are deferred on purpose, or they await a maintainer decision. They are
|
||||
not scheduled roadmap gates. When a roadmap gate depends on an item, the gate
|
||||
names it. Remove an item only when it is done, and record where it was done.
|
||||
|
||||
| Item | Raised | Why deferred | Needed before |
|
||||
|---|---|---|---|
|
||||
| **World0 break-glass membership.** Decide who may act as `aevolution:world0-break-glass`, and how that group is granted: for example a short-lived client certificate with that organization, or an OIDC group. Decide also how its use is approved and recorded. The admission policy already enforces the group (ADR-0069). | M8.2, 2026-09-29 | Maintainer: figure out later | Any intentional deletion of World0 data or identity; M8.8 World0 launch |
|
||||
| **Storage after the RAID/disk rework.** Re-run `deploy/kubernetes/inventory/disk-probe-local-path.yaml` (or a new class), and update INVENTORY.md. | M8.1, 2026-09-29 | Maintainer is reorganizing disks | M8.3's final storage decision |
|
||||
|
||||
## Accepted risks (maintainer decisions)
|
||||
|
||||
| Decision | Date | Consequence | Mitigation in place |
|
||||
|---|---|---|---|
|
||||
| Argo CD's `default` AppProject stays unrestricted | 2026-09-29 | Applications in `default` (other projects, two with automated prune) can create objects in any namespace, including AEvolution's. | The World0 admission policy denies every deletion of World0 data, identity and delivery objects, whatever the project (ADR-0069). The AEvolution projects themselves are scoped. |
|
||||
@@ -1010,3 +1010,8 @@ refuses World0.
|
||||
The offline policy check (now a CI suite) passes, and nine injected violations
|
||||
were each caught. Applying the layer and running `tools/ops/verify-isolation.sh`
|
||||
is waiting on the maintainer.
|
||||
|
||||
M8.2 applied and verified live (2026-09-29): 175 PASS and 2 SKIP. The only 3 FAILs
|
||||
were a script defect in the project check, now fixed. The maintainer accepted
|
||||
leaving Argo's `default` project unrestricted. Break-glass membership is in the
|
||||
new docs/BACKLOG.md. Next: M8.3, durable stores in dev and stage.
|
||||
|
||||
@@ -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).
|
||||
|
||||
@@ -54,6 +54,10 @@ 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:
|
||||
1. Record the operation and its approval.
|
||||
2. Use a credential whose groups include `aevolution:world0-break-glass`, for
|
||||
@@ -67,8 +71,8 @@ verify script uses server-side dry runs.
|
||||
## Residual risks
|
||||
- **`default` AppProject.** 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. Recommended: restrict
|
||||
`default`, or move those applications to scoped projects.
|
||||
namespaces. Admission denies only World0 deletions. The maintainer accepted this
|
||||
risk on 2026-09-29 and is leaving `default` as it is (docs/BACKLOG.md).
|
||||
- **World0 volumes.** `local-path` provisions volumes with Delete. Patch each World0
|
||||
PV to `Retain` when it is bound, and the policy then keeps it there. Volumes stay
|
||||
node-local until M8.3.
|
||||
|
||||
Reference in New Issue
Block a user