Skip to content

kubectl: support Go runtime execution tracing #1720

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.

Sign up for GitHub

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

Jump to bottom
Open
nsrip-dd opened this issue Feb 19, 2025 · 4 comments · May be fixed by kubernetes/kubernetes#130500
Open

kubectl: support Go runtime execution tracing #1720

nsrip-dd opened this issue Feb 19, 2025 · 4 comments · May be fixed by kubernetes/kubernetes#130500
Labels
kind/feature Categorizes issue or PR as related to a new feature. sig/cli Categorizes an issue or PR as relevant to SIG CLI. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@nsrip-dd
Copy link

What would you like to be added?

Support for running kubectl with the Go runtime execution tracer enabled.

Why is this needed?

There is already support for enabling most of the runtime profilers via the --profile option, but not for the runtime execution tracer. The tracer is useful for finding concurrency bottlenecks and understanding off-CPU time, including networking, in a way that isn't possible with any of the other Go profilers. Having it would make it easier to debug latency issues in kubectl.

I'm happy to send a PR implementing this.
@nsrip-dd nsrip-dd added the kind/feature Categorizes issue or PR as related to a new feature. label Feb 19, 2025
@k8s-ci-robot k8s-ci-robot added needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Feb 19, 2025
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@nsrip-dd
Copy link
Author

/sig cli

@k8s-ci-robot k8s-ci-robot added sig/cli Categorizes an issue or PR as relevant to SIG CLI. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Feb 19, 2025
@github-project-automation github-project-automation bot moved this to Needs Triage in SIG CLI Feb 19, 2025
@HirazawaUi
Copy link
Contributor

/transfer kubectl

@k8s-ci-robot k8s-ci-robot transferred this issue from kubernetes/kubernetes Feb 20, 2025
@mpuckett159
Copy link
Contributor

/triage accepted
This sounds like a good idea, we would be happy to accept a PR to enable this.

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Feb 26, 2025
@nsrip-dd nsrip-dd linked a pull request Feb 28, 2025 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature. sig/cli Categorizes an issue or PR as relevant to SIG CLI. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
SIG CLI
Status: Needs Triage
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

cmd/kubectl: support execution tracing nsrip-dd/kubernetes
4 participants
@mpuckett159 @k8s-ci-robot @HirazawaUi @nsrip-dd