Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ketall is too slow when there are many objects in the cluster #60

Open
corneliusweig opened this issue Jun 15, 2020 · 1 comment
Open
Assignees

Comments

@corneliusweig
Copy link
Owner

No description provided.

@tillig
Copy link

tillig commented Oct 4, 2021

Just hit this myself. I had previously written a script that basically did:

  • kubectl api-resources -o name --namespaced=true (or --namespaced=false, depending on what I'm looking for)
  • Removes anything that looks like events
  • Joins everything in a comma-delimited list
  • Does kubectl get list,of,comma,delimited,resources

...and it appears to be a lot faster than Ketall. Ketall takes 1m 49s to list the resources in a namespace; same namespace with the shell script (same resources displayed) is 16s. Adding --use-cache doesn't seem to make more than a couple seconds difference.

Granted, Ketall is doing more with respect to filtering, etc., but I'm not sure if maybe that sparks some ideas or something.

Here's my script in case you're interested.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants