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
Kubectl - flush profiling when interrupting a long running command #96019
Conversation
/sig cli |
/assign @soltysh |
Signed-off-by: Ricardo Pchevuzinske Katz <ricardo.katz@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
/triage accepted
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rikatz, soltysh The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Signed-off-by: Ricardo Pchevuzinske Katz ricardo.katz@gmail.com
What type of PR is this?
/kind bug
What this PR does / why we need it: kubectl doesn't flushes the profiling files when the run is interrupted. This PR adds the termination handling, and flushes the profile before finishing the program
Which issue(s) this PR fixes:
Fixes #96017
Special notes for your reviewer:
Actually when kubectl gets an error, it exists with os.Exit(1) from
cmdutil.CheckErr
which doesn't allow the profiler to have a chance to flush and stop either.This PR solves only the 'control-c' problem, but I can take a further look also into how to deal with the cmdutil.CheckErr to flush the profiling when an error happens (as a timeout while waiting)
Does this PR introduce a user-facing change?:
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: