Infos:
- Used Zammad version: 6.5.0
- Used Zammad installation type: kubernetes
- Operating system: debian 12
- Browser + version: Vivaldi 7.3.3635.9 / Chrome 134.0.6998.199
Expected behavior:
- Official or community-supported backup script or strategy tailored for Kubernetes environments.
- A clear and documented way to trigger backups and restores — ideally in a way compatible with Kubernetes paradigms (CronJobs, Jobs, PersistentVolumeClaims, etc.).
- Examples or documentation for backup management that consider container lifecycle and volume persistence.
Actual behavior:
- The official Zammad documentation covers backup procedures mainly for bare-metal or virtual machine installations.
- No clear or dedicated documentation found regarding backup strategies in Kubernetes environments.
- Lack of reference examples on how to handle:
- Persistent Volume backup.
- Application-consistent database and assets backup.
- Automated restore tests in Kubernetes.
In the context of Kubernetes deployments, is performing a PostgreSQL database dump (e.g., via pg_dump) sufficient to ensure a complete and reliable backup of Zammad, or are there additional files or directories (besides the database) that must be included in the backup process (e.g., attachments, configurations, state files)?
A clear list of what needs to be backed up in Kubernetes environments would be highly appreciated.