BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//pretalx.devconf.info//devconf-cz-2026//talk//EC7XDA
BEGIN:VTIMEZONE
TZID:CET
BEGIN:STANDARD
DTSTART:20001029T040000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000326T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-devconf-cz-2026-EC7XDA@pretalx.devconf.info
DTSTART;TZID=CET:20260618T144500
DTEND;TZID=CET:20260618T152000
DESCRIPTION:Distributed tracing assumes HTTP headers carry context. Kuberne
 tes-native CI/CD has no requests - causality flows through resource manife
 sts and reconciliation loops across controllers\, clusters\, and time gaps
 .\n\nThis talk introduces Controller-Native Trace Propagation: controllers
  inject W3C trace context onto Kubernetes resources they create\, and down
 stream runtimes graft execution spans under it. One trace per delivery enc
 odes stage-level causality across the Continuous Delivery lifecycle - buil
 d\, test\, and release - no custom correlation needed.\n\nUsing a Tekton-b
 ased platform\, I show how a Snapshot resource anchors trace continuity: t
 he triggering component's context propagates through integration and relea
 se\, while timestamp-derived spans decompose each stage into wait vs. exec
 ution time.\n\nThe pattern generalizes to any controller creating resource
 s with trace parent adoption. Attendees leave with a named\, reusable prop
 agation model and practical delivery latency techniques.
DTSTAMP:20260430T124928Z
LOCATION:D0206 (capacity 154)
SUMMARY:Tracing Without Requests: Controller-Native Trace Propagation for D
 elivery Analytics - Josiah England
URL:https://pretalx.devconf.info/devconf-cz-2026/talk/EC7XDA/
END:VEVENT
END:VCALENDAR