Improve platform stability: Job TTL¶
Important
- This safeguard is enabled by default and will mutate violations. As a result, resources that violate this policy will be modified with a default config so that it does follow the policy.
In Kubernetes, Jobs that are not managed by a higher-level resource such as a Cronjob, will most likely not get cleaned up automatically as Jobs do not have a default time-to-live, TTL, configured. In worst case the number of finished jobs could accumulate to such a volume that it might impact the stability of the Kubernetes cluster.
However, by default in Compliant Kubernetes, there is a policy that demands Jobs to have a TTL. Jobs that do not explicitly set a TTL (spec.ttlSecondsAfterFinished) will automatically get a TTL of 7 days.