Files
Verso/server-ce/k8s/verso-prod-pvcs.yaml
claude 0f640c74b2
Build and Deploy Verso / deploy (push) Successful in 1m18s
Prod: provision PVCs out of band (storageClass under operator control)
- Add server-ce/k8s/verso-prod-pvcs.yaml (mongo-data/redis-data/verso-data,
  ReadWriteOnce, storageClassName left for the operator to set — use a Ceph RBD
  block class).
- Drop the inline PVC definitions from deploy-verso-prod.yml so it won't fight
  the operator-provisioned PVCs; the deploy now assumes they already exist.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-03 11:36:41 +00:00

50 lines
1.4 KiB
YAML

# PersistentVolumeClaims for the prod (verso namespace) instance.
#
# Provisioned out of band (not by the deploy workflow) so the storageClass is
# under your control. Create them ONCE, before the first prod deploy:
#
# kubectl apply -f server-ce/k8s/verso-prod-pvcs.yaml
#
# Use a Ceph RBD (block) storageClass for all three — every volume here is
# single-writer ReadWriteOnce (Mongo, Redis, and the single app pod). Set
# storageClassName below to your RBD class (run `kubectl get storageclass` to
# find its name). Sizes are starting points; RBD supports online expansion.
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: mongo-data
namespace: verso
spec:
accessModes: [ReadWriteOnce]
# storageClassName: ceph-rbd # <- set to your RBD (block) storageClass
resources:
requests:
storage: 10Gi
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: redis-data
namespace: verso
spec:
accessModes: [ReadWriteOnce]
# storageClassName: ceph-rbd # <- set to your RBD (block) storageClass
resources:
requests:
storage: 2Gi
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: verso-data
namespace: verso
# verso-data is mounted at /var/lib/overleaf/data: user files, compiles, output
# cache, and published-presentation snapshots.
spec:
accessModes: [ReadWriteOnce]
# storageClassName: ceph-rbd # <- set to your RBD (block) storageClass
resources:
requests:
storage: 20Gi