According to Kubernetes documentation startingDeadlineSeconds "stands for the deadline in seconds for starting the job if it misses its scheduled time for any reason. After the deadline, the cron job does not start the job. Jobs that do not meet their deadline in this way count as failed jobs."
By default our prune job is being configured with this parameter set to 60 seconds, and according to discussions, due to performance constraints, the job may not be spawned in time.
We need to increase the default value to assure pruner job will run
Verified on 4.5.0-0.nightly-2020-05-30-025738:
$ oc get cronjob image-pruner -o yaml | grep startingDeadlineSeconds
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.