589819682e
Fixes #2170 The number of days to delay file replication deletion by is configurable in the Helm chart with `replica_deletion_delay_days` (set by default to 7 days in `values.yaml` to encourage good practice, though we could change this). When `replica_deletion_delay_days` is set to an int above 0, when a delete replica job would otherwise be started as a Kubernetes Job, a CronJob is created instead with a cron schedule set to run yearly, starting x days from the current moment. This cronjob is then deleted by the operator after the job successfully completes. If a failed background job is retried, it is re-run immediately as a Job rather than being scheduled out into the future again. --------- Co-authored-by: Ilya Kreymer <ikreymer@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| background_job.yaml | ||
| crawl_configmap.yaml | ||
| crawl_cron_job.yaml | ||
| crawl_job.yaml | ||
| crawler.yaml | ||
| profile_job.yaml | ||
| profilebrowser.yaml | ||
| qa_configmap.yaml | ||
| redis.yaml | ||
| replica_deletion_cron_job.yaml | ||
| replica_job.yaml | ||