Add M8.2 environment isolation and World0 protection
Per-environment platform layers (dev, stage, world0) with restricted pod security, quotas, limit ranges, default-deny networking and token-less service accounts, applied by an administrator rather than Argo. A native ValidatingAdmissionPolicy denies deleting World0 data, identity and Argo objects to every requester without the break-glass group. Stage and World0 Argo projects are scoped to one namespace, World0 blocks automated sync, and a cleanup tool refuses World0. An offline policy check runs as a new CI suite; a live verification script uses only can-i, reads and server dry runs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -2639,3 +2639,27 @@ Evidence:
|
||||
- Collection is manual, with no automation planned.
|
||||
- No credential values were read. The 18.6 version, role and TLS requirements are
|
||||
enforced by the adapter and migrations when M8.3 connects.
|
||||
|
||||
## M8.2 environment isolation - 2026-09-29
|
||||
|
||||
- `tools/ci/deploy-policy-check.py` (WSL, Python 3 with PyYAML): 35 objects in 27
|
||||
files, 0 failures.
|
||||
- Nine mutations were each caught, then restored:
|
||||
- World0 auto-sync;
|
||||
- the World0 cascade finalizer;
|
||||
- the policy set to failurePolicy Ignore;
|
||||
- the policy no longer covering Secrets;
|
||||
- an egress hole in default-deny;
|
||||
- the World0 protected label removed;
|
||||
- the cleanup tool accepting world0 (rc 127, it reached kubectl);
|
||||
- service-account token automount;
|
||||
- a wildcard stage destination.
|
||||
- `kubectl kustomize` (client v1.31.4) renders the dev, stage and World0 platform
|
||||
overlays (9 objects each), and still renders the live `deploy/kubernetes/dev`
|
||||
path unchanged.
|
||||
- `bash -n` passes for both ops scripts.
|
||||
- The CI `deploy` suite (a Docker `ci-deploy` stage) has not run yet; Docker is
|
||||
not running locally.
|
||||
- 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`.
|
||||
|
||||
Reference in New Issue
Block a user