gerlowskija opened a new issue #303: URL: https://github.com/apache/solr-operator/issues/303
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? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
