Files
aevolution/deploy/argocd/world0/project.yaml.example
T
dingoandClaude Opus 5.5 df0c4f4efb 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>
2026-09-29 12:43:58 -04:00

34 lines
1.1 KiB
Plaintext

# M8.2 (world0). Apply by hand to the argocd namespace; never from an Application.
# One destination namespace only, no cluster-scoped kinds, no Secrets or quotas.
apiVersion: argoproj.io/v1alpha1
kind: AppProject
metadata:
name: aevolution-world0
namespace: argocd
spec:
description: AEvolution world0 (evolution-world0 only)
sourceRepos:
- https://git.aeternalisgames.com/dingo/AEvolution.git
destinations:
- server: https://kubernetes.default.svc
namespace: evolution-world0
clusterResourceWhitelist: []
namespaceResourceWhitelist:
- {group: "", kind: Service}
- {group: "", kind: ConfigMap}
- {group: "", kind: PersistentVolumeClaim}
- {group: apps, kind: Deployment}
- {group: batch, kind: Job}
- {group: networking.k8s.io, kind: NetworkPolicy}
# Not listed, so never Argo-managed: Namespaces, ServiceAccounts (platform layer),
# Secrets, quotas, limit ranges and RBAC.
orphanedResources:
warn: true
# No automated sync can ever run; a human may still sync by hand.
syncWindows:
- kind: deny
schedule: "* * * * *"
duration: 24h
applications: ["*"]
manualSync: true