A CronJob writes intermediate files to an emptyDir during each run. A developer assumes last night’s emptyDir data is still there for tonight’s Job. What is true?
Select an answer to reveal the explanation.
Short Explanation
Every CronJob tick spins up a fresh Pod—like a new scratch pad each morning. emptyDir dies with that Pod, so last night’s files are gone. Design the Job to fetch inputs again or use real persistence if you need carry-over.
Full Explanation
CronJob runs create Job objects that launch new Pods. An emptyDir volume is ephemeral to each Pod and does not persist across Job executions. History limits affect retained Job objects for inspection, not emptyDir contents. Use a PVC or external storage when data must survive between runs.