Keep the filesystem object store on a node-local Retain-class PVC per environment (ADR-0070), with the database on the external PostgreSQL VM. Because local-path does not enforce sizes, the object store now refuses new objects below a free-space reserve with a distinct full error, so a full volume publishes and acknowledges nothing. evo-world-clone gains check-store to qualify volume retention, reserve, database version/TLS and the runtime privilege boundary from inside the cluster; it now ships in the server image. Add the storage class, object claims, hand-applied store Jobs, policy rules forbidding password env vars, and the runbook. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
16 lines
603 B
YAML
16 lines
603 B
YAML
# M8.3 region object store volume (ADR-0070): durable data, so it belongs to the
|
|
# platform layer (applied by hand), never to an Argo Application. The volume is
|
|
# created on the node of its first consumer; every consumer selects
|
|
# aevolution.io/stores=true, so label exactly one worker first (ENVIRONMENTS.md).
|
|
# Retain: deleting this claim leaves the volume and its data Released, not deleted.
|
|
apiVersion: v1
|
|
kind: PersistentVolumeClaim
|
|
metadata:
|
|
name: aevolution-objects
|
|
spec:
|
|
accessModes: [ReadWriteOnce]
|
|
storageClassName: aevolution-local-retain
|
|
resources:
|
|
requests:
|
|
storage: 10Gi
|