The Legend of Config: Breath of the Cluster
summary
Demonstrates that OpenTelemetry plus eBPF (OBI) reveals network flows but misses route and policy context, so a custom Gateway API processor is built for the collector that watches Gateway API and mesh CRDs, caches them, and enriches spans with attributes like kubernetes.gateway.name and kubernetes.httproute.name. Shows the processor integrating with existing Kubernetes attribute processors, reduces manual kubectl digging, and works end-to-end though it’s experimental and not yet in contrib.
AI-written summary · about
chapters (10)
- 0:00Kubernetes networking intro
- 2:08Gateway API routing challenges
- 3:30Ingress to Gateway API
- 5:58GAMMA service mesh initiative
- 9:27Gateway API AI extensions
- 11:11Service mesh observability
- 12:59Debugging with span flags
- 16:29Oboe troubleshooting limits
- 19:17Gateway API processor intro
- 22:27Future of Gateway processor
related talks
27mStep By Step Kubernetes Observability with eBPF
34mStep by Step Kubernetes Observability with eBPF
22mHarnessing Observability for 5G Performance: eBPF and OpenTelemetry I...
26mObservability at the Edge: State of OpenTelemetry in Kubernetes Ingress Contro...
31mTrue Kubernetes Observability with eBPF
34mNetwork Observability with eBPF and OpenTelemetry
32mOpenTelemetry Gateways: Enforce, Transform, Route
22mUnified Observability