You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: keps/sig-instrumentation/2831-kubelet-tracing/README.md
+9-5
Original file line number
Diff line number
Diff line change
@@ -143,7 +143,10 @@ OpenTelemetry-Go provides the [propagation package](https://github.com/open-tele
143
143
144
144
### Connected Traces with Nested Spans
145
145
146
-
Nested spans with top-level traces in the kubelet will connect CRI calls together. Nested spans will be created for the following:
146
+
With the initial implementation of this proposal, kubelet tracing produced disconnected spans, because context was not wired through kubelet CRI calls.
147
+
With [this PR](https://github.com/kubernetes/kubernetes/pull/113591), context is now plumbed between CRI calls and kubelet.
148
+
It is now possible to connect spans for CRI calls. Nested spans with top-level traces in the kubelet will connect CRI calls together.
149
+
Nested spans will be created for the following:
147
150
* Sync Loops (e.g. syncPod, eviction manager, various gc routines) where the kubelet initiates new work.
148
151
*[top-level traces for pod sync and GC](https://github.com/kubernetes/kubernetes/pull/114504)
0 commit comments