Ben Hardill#Kubernetes question. The #mastodon helm chart sets up a cron job that runs every Sunday morning to clean up the media cache, this appears to leave Job pods in the `kubectl get pods` list. Should they clean themselves up or do I run `kubectl delete pod` on the `Completed` items?
Nevermind, I've found `successfulJobsHistoryLimit`
Marcus Noble@ben if you’re running at least Kubernetes v1.23 then you can add this: https://kubernetes.io/docs/concepts/workloads/controllers/ttlafterfinished/
Automatic Clean-up for Finished Jobs
FEATURE STATE: Kubernetes v1.23 [stable] TTL-after-finished controller provides a TTL (time to live) mechanism to limit the lifetime of resource objects that have finished execution. TTL controller only handles Jobs. TTL-after-finished Controller The TTL-after-finished controller is only supported for Jobs. A cluster operator can use this feature to clean up finished Jobs (either Complete or Failed) automatically by specifying the .spec.ttlSecondsAfterFinished field of a Job, as in this example. The TTL-after-finished controller will assume that a job is eligible to be cleaned up TTL seconds after the job has finished, in other words, when the TTL has expired.
Nico -telmich- Schottelius@ben Checkout the cleanupPolicy on https://kubernetes.io/docs/concepts/workloads/controllers/job/#job-termination-and-cleanup that is taking care of the cleanup schedule
johannes_sonner@ben if you are monitoring your cluster, watch out that somenof the k8s metrics take finished jobs in consideration as well ;)