Why do jobs have to be idempotent - kubernetes cron jobs

0 votes

The documentation says the following:

A cron job creates a job object about once per execution time of its schedule. We say “about” because there are certain circumstances where two jobs might be created, or no job might be created. We attempt to make these rare, but do not completely prevent them. Therefore, jobs should be idempotent

Could anyone explain why would this happen and how can i get it fixed?

Sep 17, 2018 in Kubernetes by Hannah
• 15,340 points
287 views

1 answer to this question.

0 votes

To understand why this happens lets for instance take the node hosting the CronJobController, this node fails at the time a job is supposed to run.

The reason why this occurs is because there are no idemopotency-related issues under the area/batch label in the k8s repo, so one would guess not.

answered Sep 17, 2018 by Kalgi
• 41,590 points

Related Questions In Kubernetes

0 votes
1 answer

How do I sign-in to kubernetes dashboard?

Since version 1.7 Dashboard uses more secure ...READ MORE

answered Sep 7, 2018 in Kubernetes by DareDev
• 6,810 points
153 views
0 votes
1 answer

Connect to existing pod, execute script, disconnect - Kubernetes cron job

As far as i know there's no ...READ MORE

answered Sep 17, 2018 in Kubernetes by Kalgi
• 41,590 points
779 views
0 votes
1 answer

Do not wantthe cron job to restart with failure

you have to set a backoffLimit: 0 in combination ...READ MORE

answered Sep 18, 2018 in Kubernetes by Kalgi
• 41,590 points
197 views
0 votes
1 answer
0 votes
3 answers

Error while joining cluster with node

Hi Kalgi after following above steps it ...READ MORE

answered Jan 17 in Others by anonymous
2,573 views
+3 votes
1 answer
0 votes
1 answer
0 votes
1 answer

image can't be pulled error when I try to pull a docker image - kubernetes

I think the image is being pulled ...READ MORE

answered Sep 4, 2018 in Kubernetes by Kalgi
• 41,590 points
612 views