A design thesis for closing the pod-startup gap: combine the Kubernetes API's phase boundaries with eBPF's syscall-level evidence, correlated by pod identity and persisted before the pod disappears.
A survey of what eBPF observability tools, continuous profilers, and generic APM platforms actually do today, and why none of them attribute pod startup latency to a phase or a syscall.
What a slow Kubernetes pod startup actually costs in autoscaling, CI/CD, and on-call time, and why kubectl events and kubelet's own latency metric can't answer which pod, which second, or why.