Backups can now be kept for a period instead of a count

Backup schedules can now keep backups for a period instead of a count: retention: {type: time, duration: 30d}, with Nd, Nw, or Nm durations. The PostgreSQL provider supports time-based retention now.

Previously, schedules could only retain a number of copies. The MongoDB and MySQL operators still support only count-based retention, so those providers report type: time on the BackupConfigured condition, and the UI still edits count retention only. Note for upgraders: schedules[].retentionCopies: 7 becomes retention: {type: count, count: 7}, and after the CRD upgrade retentionCopies is pruned — affected schedules keep every backup until retention is set.

Time-based retention is available in OpenEverest 2.0.0 Developer Preview 4, installed on a fresh cluster. To learn more, visit the documentation.