kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

clarify how trace context works for kubelet tracing

pull/43168/head
David Ashpole 2023-09-22 17:54:52 +00:00
parent 0ee79d3ef8
commit fec3ca793f
No known key found for this signature in database
GPG Key ID: 563A85007BFA1BA2
1 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
content/en/docs/concepts/cluster-administration/system-traces.md
View File

@ -105,8 +105,12 @@ span will be sent to the exporter.
The kubelet in Kubernetes v{{< skew currentVersion >}} collects spans from The kubelet in Kubernetes v{{< skew currentVersion >}} collects spans from
the garbage collection, pod synchronization routine as well as every gRPC the garbage collection, pod synchronization routine as well as every gRPC
method. Connected container runtimes like CRI-O and containerd can link the method. The kubelet propagates trace context with gRPC requests so that
traces to their exported spans to provide additional context of information. container runtimes with trace instrumentation, such as CRI-O and containerd,
can associate their exported spans with the trace context from the kubelet.
The resulting traces will have parent-child links between kubelet and
container runtime spans, providing helpful context when debugging node
issues.
Please note that exporting spans always comes with a small performance overhead Please note that exporting spans always comes with a small performance overhead
on the networking and CPU side, depending on the overall configuration of the on the networking and CPU side, depending on the overall configuration of the