-
Notifications
You must be signed in to change notification settings - Fork 158
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
Restrict workload selection #62
Comments
Now I hit an issue when Prometheus is unable to give me the results and the request fails with 431. I don't understand the details
|
Thanks for reporting it @dohnto-s1 I think this issue is similar to #60 Does limiting |
This unfortunately happens when running with |
Thanks for the update. We'll try to fix it soon. |
Hey, sorry for long time waiting :) It looks like your issue could be handled by #96 If it does not, please provide logs after running with |
And I really like your proposal for selector flag, we should 100% implement it |
@LeaveMyYard Looks awesome, thanks! EDIT: Let me test it first on some of my use-cases. |
Is your feature request related to a problem? Please describe.
One might have a huge cluster and want to focus on optimizing just a particular workload.
Prometheus queries while analysing all worklaods in a cluster/namespace might take too long otherwise.
Describe the solution you'd like
Introduce a new command line argument as kubectl has:
to limit the workload selection. E. g:
Describe alternatives you've considered
Additional context
Thanks for this wonderful tool. Happy to learn if there is alternative solution for me.
The text was updated successfully, but these errors were encountered: