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>
11 lines
344 B
YAML
11 lines
344 B
YAML
# Disposable development. Existing namespace; applying adds labels and guardrails.
|
|
apiVersion: v1
|
|
kind: Namespace
|
|
metadata:
|
|
name: evolution-dev
|
|
labels:
|
|
aevolution.io/environment: dev
|
|
pod-security.kubernetes.io/enforce: restricted
|
|
pod-security.kubernetes.io/enforce-version: v1.32
|
|
pod-security.kubernetes.io/warn: restricted
|