-
Notifications
You must be signed in to change notification settings - Fork 187
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
[RFE] PoC: top cpu/memory #2825
Comments
If it's easy enough to support it from the IG core and provides enough value for many use cases, we can introduce it as a helper DataSource that can be activated from just the gadget.yaml by adding an annotation to the gadget. In this case (CPU/mem) it could just take an additional parameter for the interval whenever activated and then create a new DataSource and emit the values for every interval. |
But we were considering make it a gadget, not a complement for other gadgets. Or did I misunderstand what you said? |
Sure, but does it matter where information is coming from? If it's easy to maintain and can be useful in different scenarios, IMHO providing such functionality from the core is okay (WASM or spawning other binaries always increases overhead and in the latter case could also raise security concerns.) |
PoC: top cpu/memory
Several people in the community is asking why we don’t have a gadget like top block-io, that shows the pods consuming more CPU/memory.
Q&A from IG meeting:
kubectl top
? Yes, but:kubectl top
does.The text was updated successfully, but these errors were encountered: