From fec3ca793f67cee81e72fc7323216819164ba9e7 Mon Sep 17 00:00:00 2001 From: David Ashpole Date: Fri, 22 Sep 2023 17:54:52 +0000 Subject: [PATCH] clarify how trace context works for kubelet tracing --- .../docs/concepts/cluster-administration/system-traces.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/content/en/docs/concepts/cluster-administration/system-traces.md b/content/en/docs/concepts/cluster-administration/system-traces.md index 52cf194a88..aaaf342b57 100644 --- a/content/en/docs/concepts/cluster-administration/system-traces.md +++ b/content/en/docs/concepts/cluster-administration/system-traces.md @@ -105,8 +105,12 @@ span will be sent to the exporter. The kubelet in Kubernetes v{{< skew currentVersion >}} collects spans from the garbage collection, pod synchronization routine as well as every gRPC -method. Connected container runtimes like CRI-O and containerd can link the -traces to their exported spans to provide additional context of information. +method. The kubelet propagates trace context with gRPC requests so that +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 on the networking and CPU side, depending on the overall configuration of the