Add count/jobs.batch
quota of 150 to organization-objects
resourcequota
#139
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 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
,dependency
as they show up in the changelog.