We've observed that large amounts of completed jobs (and associated pods) can cause increased resource consumption in control plane components (e.g. apiserver memory usage). We've also observed noticeable kubectl lag for operations like kubectl get pods -A.
We've picked an initial limit of 150 jobs which should be sufficient for regular uses (e.g. appuio-cloud-reporting currently has 57 jobs in the namespace).
Checklist
[x] PR contains a single logical change (to build a better changelog).
[x] Update the documentation.
[x] Categorize the PR by setting a good title and adding one of the labels:
bug, enhancement, documentation, change, breaking, dependency
as they show up in the changelog.
We've observed that large amounts of completed jobs (and associated pods) can cause increased resource consumption in control plane components (e.g. apiserver memory usage). We've also observed noticeable
kubectllag for operations likekubectl get pods -A.We've picked an initial limit of 150 jobs which should be sufficient for regular uses (e.g. appuio-cloud-reporting currently has 57 jobs in the namespace).
Checklist
bug,enhancement,documentation,change,breaking,dependencyas they show up in the changelog.