Repository navigation
fix(kubernetes): list cluster objects in pages - #956
Merged
Merged
Conversation
pipozzz
force-pushed
the
fix/k8s-list-pages
branch
from
November 13, 2026 16:33
990ad13 to
7d67cfd
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Services, Ingresses, HTTPRoutes, Argo CD Applications and AppProjects, and Flux objects were listed in one response each. They are now read in pages of 500 (client-go pager), and Argo CD applications and services are no longer all held at once, which lowers the agent's peak memory on large clusters.
🤖 Generated with Claude Code