TaskRun notification tracing added
Security status unclearReconcileRunObject path used by CustomRunPreviously, failures could not be correlated or latency measured between the reconciliation trigger and final CloudEvent emission. Linked spans now trace this path; the TaskRun root span includes taskrun.name and taskrun.namespace, and the CloudEvent span records network and sink failures.
Show release-note lines
* :sparkles: feat(tracing): add spans to TaskRun notifications controller (#9912) Added OpenTelemetry tracing to the TaskRun notification reconciliation path. Spans now cover ReconcileKind, ReconcileRunObject, and EmitCloudEvents, enabling operators to trace CloudEvent delivery latency end-to-end.github.com/tektoncd/pipeline/releases/tag/v1.13.0