Allow backup cronjob to define custom `restartPolicy` and `activeDeadlineSeconds`
Summary
We are affected by this issue #2555 (closed), we initially planned to let the backup run (as some of their executions succeed) but do not allow it to restart, as each execution takes hours and we don't want to have it running during business hours.
Steps to reproduce
Not relevant
Configuration used
Not relevant
Current behavior
restartPolicy
is now hardcoded https://gitlab.com/gitlab-org/charts/gitlab/-/blob/master/charts/gitlab/charts/toolbox/templates/backup-job.yaml#L34 and activeDeadlineSeconds
is not present.
Check https://kubernetes.io/docs/concepts/workloads/controllers/job/#job-termination-and-cleanup for a detailed explanation of both parameters.
Expected behavior
Let the user decide which restartPolicy
to use and optionally set a activeDeadlineSeconds
.
Versions
Not relevant
Relevant logs
Not relevant