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
Change tracing service from kube-apiserver to apiserver #103435
Conversation
/priority important-soon |
/sig instrumentation api-machinery |
/lgtm |
/triage accepted |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dashpole, liggitt 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 |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Address feedback from the initial tracing PR: #94942 (review)
The library can be used by things other than the kube-apiserver, so this renames it to apiserver.
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:
/assign @liggitt