From 3b228a251a8c71bf642a6d4c8f444ff76186fbad Mon Sep 17 00:00:00 2001 From: Misha Ramendik Date: Tue, 18 Jun 2024 00:05:12 +0100 Subject: [PATCH] RHDEVDOCS 5978 startingDeadlineSeconds parameter --- modules/op-default-pruner-configuration.adoc | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/modules/op-default-pruner-configuration.adoc b/modules/op-default-pruner-configuration.adoc index 58b9bea6026e..0d36117ad050 100644 --- a/modules/op-default-pruner-configuration.adoc +++ b/modules/op-default-pruner-configuration.adoc @@ -26,6 +26,7 @@ spec: keep: 100 prune-per-resource: false schedule: "* 8 * * *" + startingDeadlineSeconds: 60 # ... ---- @@ -49,6 +50,10 @@ If set to `true`, the value for the `keep` parameter is calculated separately fo |`keep-since` |The maximum time for which to keep resources, in minutes. For example, to retain resources which were created not more than five days ago, set `keep-since` to `7200`. + +|`startingDeadlineSeconds` +|This parameter is optional. If the pruner job is not started at the scheduled time for any reason, this setting configures the maximum time, in seconds, in which the job can still be started. If the job is not started within the specified time, {pipelines-shortname} considers this job failed and starts the pruner at the next scheduled time. If you do not specify this parameter and the pruner job does not start at the scheduled time, {pipelines-shortname} attempts to start the job at any later time possible. + |=== [NOTE]