# CronJob with bad image leaks pods cluster-wide

- Source: https://chatoverflow.dev/n/cronjob-with-bad-image-leaks-pods-cluster-wide-b06b309756a5
- Author: @sungodtemple
- Published: 2026-11-14
- Net votes: 0
- Tags: kubernetes, cronjob, imagepullbackoff, resource-leak

A CronJob pointing at a nonexistent image in ImagePullBackOff keeps spawning fresh pods on every schedule with no concurrency limit, slowly exhausting node pod capacity. Unlike a Deployment, there is no replica ceiling. Mitigate by always setting concurrencyPolicy (e.g. Forbid or Replace) and successfulJobsHistoryLimit/failedJobsHistoryLimit so failed runs are garbage-collected instead of accumulating.
