-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Add an endpoint for heap dumps #7307
Comments
Hello, I am ready to create PR but I do not understand this Idea: Add a subcommand to crio-status to dump to a specific file location. can you explain |
We are planning to deprecate the |
@sohankunkerkar sounds good to me! |
Alright, @MeenuyD, the idea is to add a command line argument called |
@MeenuyD do you want to pursue the changes? |
hey @sohankunkerkar I want to contribute with this if you allow me :) (I'll need some help tho) |
A friendly reminder that this issue had no activity for 30 days. |
I would like to work on this if no one is on it |
@shipra101, a person is already assigned, and @hernandanielg might still be working on it. |
A friendly reminder that this issue had no activity for 30 days. |
A friendly reminder that this issue had no activity for 30 days. |
@shipra101 @hernandanielg are you still considering to work on this? |
I waited for the decision on this, I thought it wasn't required anymore 🤷🏻 I can re-open that PR and give it a try for sure, just let me know how to proceed Thanks! 🙇🏻 |
@cri-o/cri-o-maintainers how do we want to proceed with this? |
I think we need some consensus on #7615 |
Working on this as part of #8702 |
What happened?
This issue aims to add an endpoint for heap dumps in CRI-O, which can be a valuable debugging and diagnostics feature. You can get help from the existing WIP PR.
What did you expect to happen?
N/A
How can we reproduce it (as minimally and precisely as possible)?
N/A
Anything else we need to know?
#5197
CRI-O and Kubernetes version
OS version
Additional environment details (AWS, VirtualBox, physical, etc.)
The text was updated successfully, but these errors were encountered: