Hi,

Thank you for your clarification. In order to accomplish this on our platform you unfortunately would need to use a more “creative” workaround. Off the top of my head I would consider the following options:

1. Create a third job along with the other ones that runs a one-liner to cleanup all the jobs. I have validated cleanup could work with this command:
   kubectl delete pod --field-selector=status.phase=Succeeded
   For redundancy you can also add additional labels to your job’s pods to ensure you’re not deleting any other pods like so:
   kubectl delete pod -l job=job1 –field-selector=status.phase=Succeeded
   That will ensure that the pods being deleted will have the job=job1 label to even be considered for deletion.

2. Create Kubernetes cronjob to cleanup your other Job pods, then you can then use the limits mentioned above to have the cronjobs clean themselves up.

3. Create local linux cronjob to run the command from #1 locally on your machine.

4. Depending on the job you could look to include those tasks in your deployments init-containers instead. https://kubernetes.io/docs/concepts/workloads/pods/init-containers/

I would recommend you add this topic to https://ideas.digitalocean.com. That is reviewed from time to time to gauge feature request priority.

Let me know if you have any additional questions.

Regards,

John Kwiatkoski
Senior Developer Support Engineer