CODEWITHSUNDEEP
kuberneteskubernetes-cronjob
macetw
macetw

Reputation: 1820

Kubernetes concurrencyPolicy Forbid not preventing concurrent jobs

I have a backup job running, scheduled to run every 24 hours. I have the concurrency policy set to "Forbid." I am testing my backup, and I create jobs manually for testing, but these tests are not forbidding concurrent runs. I use:

kubectl create job --from=cronjob/my-backup manual-backup-(timestamp)

... and when I run them twice in close succession, I find that both begin the work.

Does the concurrency policy only apply to jobs created by the Cron job scheduler? Does it ignore manually-created jobs? If it is ignoring those, are there other ways to manually run the job such that the Cron job scheduler knows they are there?

Upvotes: 1

Views: 2318

Answers (1)

gohm'c
gohm'c

Reputation: 15490

...Does the concurrency policy only apply to jobs created by the Cron job scheduler?

concurrencyPolicy applies to CronJob as it influences how CronJob start job. It is part of CronJob spec and not the Job spec.

...Does it ignore manually-created jobs?

Yes.

...ways to manually run the job such that the Cron job scheduler knows they are there?

Beware that when concurrencyPolicy is set to Forbid and when the time has come for CronJob to run job; but it detected there is job belongs to this CronJob is running; it will count the current attempt as missed. It is better to temporary set the CronJob spec.suspend to true if you manually start a job base out of the CronJob and the execution time will span over the next schedule time.

Upvotes: 3

Related Questions