Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
It seems like pods created by a Kubernetes CronJob (or rather Job) are deleted as soon as they fail. This makes it difficult to figure out what went wrong (unless you have Prometheus or some other ...
#1: Initial revision
by
Iizuki
·
2025-01-30T07:16:07Z (6 days ago)
Keep failed CronJob Pods around in Kubernetes
It seems like pods created by a Kubernetes CronJob (or rather Job) are deleted as soon as they fail. This makes it difficult to figure out what went wrong (unless you have Prometheus or some other log aggregator in use). Is there a way to keep the pods of the failed Jobs around for a while to facilitate post mortem analysis?