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>
18 lines
481 B
YAML
18 lines
481 B
YAML
# Defaults for containers that omit resources (the quota requires them), sized from
|
|
# the measured region-host profile (peak RSS about 9.7 MiB): 64Mi request, 256Mi
|
|
# limit, 50m CPU request and no default CPU limit. No container may exceed 2Gi.
|
|
apiVersion: v1
|
|
kind: LimitRange
|
|
metadata:
|
|
name: aevolution-defaults
|
|
spec:
|
|
limits:
|
|
- type: Container
|
|
defaultRequest:
|
|
cpu: 50m
|
|
memory: 64Mi
|
|
default:
|
|
memory: 256Mi
|
|
max:
|
|
memory: 2Gi
|