Currently, each ‘solrbackup’ resource triggers a one-time backup of the specified collections. This is great for many usecases that only need backups on an ad-hoc basis, but it falls short on SaaS or other hosted usecases that often take backups on a regular schedule as a basic precaution.

Operator users should be able to configure a schedule (either in the existing ‘solrbackup’ CRD, or in a new ‘solrbackupschedule’ resource type) so that backups can be set up to recur without further intervention. Ideally some sort of “maxBackupsRetained” setting would also be added to garbage-collect old backups that are no longer needed I guess?