The libraries that implement open-tracing typically use a very lightweight network connection, in this case UDP, to send traces from our code. UDP does not guarantee connections, so this also means that trace information could be lost if the network became too congested. OpenTracing and Jaeger minimize that by taking advantage of one of the guarantees of Kubernetes: two containers in the same pod will be placed on the same node, sharing the same network space. If we run a process in another container in our pod that captures the UDP packets, the network connectivity will be all on the same node and have very little chance of interference.
The Jaeger project has an image that listens to a variety of ports ...
