Files
jasonwittyandClaude Opus 5 91d96eb17a
Validate and Deploy to K3s / validate (push) Failing after 23s
Validate and Deploy to K3s / deploy (push) Skipped
Add limesurvey, migrating its data off local-path onto GlusterFS
LimeSurvey was never in this repo, and its two PVCs used the k3s local-path
StorageClass: both volumes were pinned to rpi-worker-3's local disk with
persistentVolumeReclaimPolicy: Delete. That put the survey data on a single
SD-backed node with no replication, where deleting the PVC would destroy it.

Both volumes now live on gvolume0 under /mnt/gvolume0/limesurvey/{app,db},
with Retain, matching the pattern used by vaultwarden and tududi. Migrated
2026-09-21 via mysqldump/restore; verified identical afterwards (3 surveys,
742 responses, 2 users, 17 questions, 60 tables).

db-config.yaml is required, not optional: InnoDB's defaults assume a local
POSIX filesystem, and on a GlusterFS FUSE mount native AIO is unavailable and
O_DIRECT unreliable. Without innodb_use_native_aio=0 and
innodb_flush_method=fsync, MariaDB either fails to start or risks corruption.

A nightly dump to /mnt/gvolume0/limesurvey/backups (14 day retention) is
included -- a volume survives losing a node, but a logical dump also survives
corruption, a bad upgrade and mistaken deletes.

The old local-path PVCs (limesurvey-db-data, limesurvey-uploads) are
deliberately left in place as a rollback and are not managed here.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-20 19:54:29 -07:00

46 lines
1.6 KiB
YAML

# Added 2026-09-21. The datadir now lives on GlusterFS, which survives losing a
# node -- but a logical dump also survives corruption, a bad upgrade, and
# fat-fingered deletes, which a volume does not. Keeps 14 days.
apiVersion: batch/v1
kind: CronJob
metadata:
name: limesurvey-db-backup
namespace: limesurvey
spec:
schedule: "17 3 * * *"
concurrencyPolicy: Forbid
successfulJobsHistoryLimit: 2
failedJobsHistoryLimit: 3
jobTemplate:
spec:
template:
spec:
restartPolicy: OnFailure
containers:
- name: dump
image: docker.io/library/mariadb:11
env:
- name: MARIADB_ROOT_PASSWORD
valueFrom:
secretKeyRef:
name: limesurvey
key: db-root-password
command:
- sh
- -c
- |
set -e
f=/backups/limesurvey-$(date -u +%Y%m%d-%H%M%S).sql.gz
mariadb-dump -h limesurvey-db -u root -p"$MARIADB_ROOT_PASSWORD" \
--single-transaction --routines --triggers --events \
--databases limesurvey | gzip > "$f"
echo "wrote $f ($(stat -c%s "$f") bytes)"
find /backups -name 'limesurvey-*.sql.gz' -mtime +14 -delete
volumeMounts:
- name: backups
mountPath: /backups
volumes:
- name: backups
persistentVolumeClaim:
claimName: limesurvey-backups