<p>According to <a href="https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/#cron-job-limitations" rel="nofollow noreferrer">this page</a> in K8S,
"...two jobs might be created...".</p>

<p>If I set my <code>concurrencyPolicy</code> to "Forbid" - Will I still get optionally concurrent runs due to the scheduler, or will I get concurrent calls to run but be prevented?</p>

<p>I also opened an issue in the Docs site:
<a href="https://github.com/kubernetes/website/issues/18655" rel="nofollow noreferrer">https://github.com/kubernetes/website/issues/18655</a></p>

Shachar Silbert
<p>Setting concurrencyPolicy to "Forbid" will make it so that if, by the time the next scheduled job comes around, the previous job is still running cron will not spin up another job and will count as a missed job.
Setting it to "Allow" will allow these jobs to run at least once when scheduled.</p>

<p>There is only a chance of two jobs, or no job, being run at one scheduled time as K8S does not fully prevent this.</p>
