fix: Correct limit in controller List API calls. Fixes #11134 #11343
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.
Fixes #11134.
The reason for this change is that
resourceVersion=0
does not honor thelimit
in API calls (related issue kubernetes/kubernetes#59684 (comment)), which results in making significant LIST calls withoutlimit
. Below are some screenshots from experiments (credit to Jesse). Same results for other non-pod resources.Even though we may see
limit=100&resourceVersion=0
in the controller logs, the API server does not honor the limit.