d155fb78ca
The Cronjob controller will check every 10s if there is a job to start, but if there are more than 100 retries to start the job, it will fail with "Cannot determine if job needs to be started. Too many missed start time (> 100). Set or decrease .spec.startingDeadlineSeconds or check clock skew." error. If the Cronjob controller happens to be down for a long period and 100 retries occured since lastScheduledTime, after that it will NOT retry to run the job. Because concurrencyPolicy is set to Forbid and startingDeadlineSeconds was not set, the Cronjob controller will fail to start a new job when another job is already running and will increase an internal counter. If startingDeadlineSeconds is set, the Cronjob controller will count how many fails occured in the last startingDeadlineSeconds seconds. Closes-bug: 1913057 Signed-off-by: Daniel Safta <daniel.safta@windriver.com> Change-Id: I3ca5ad04290580a8d0bf20f787cf5eefef6ac422 |
||
---|---|---|
.. | ||
files | ||
helm-charts | ||
manifests | ||
README |
README
This directory contains all StarlingX charts that need to be built to support platform integration immediately after installation. Some charts are common across applications. These common charts reside in the stx-config/kubernetes/helm-charts directory. To include these in this application update the build_srpm.data file and use the COPY_LIST_TO_TAR mechanism to populate these commom charts.