Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
virtcontainers: clh: Do not use the default HTTP client
When enabling tracing with Cloud Hypervisor, we end up establishing 2 connections to 2 different HTTP servers: The Cloud Hypervisor API one that runs over a UNIX socket and the Jaeger endpoint running over UDP. Both connections use the default HTTP golang client instance, and thus share the same transport layer. As the Cloud Hypervisor implementation sets it up to be over a Unix socket, the jaeger uploader ends up going through that transport as well, and sending its spans to the Cloud Hypervisor API server. We fix that by giving the Cloud Hypervisor implementation its own HTTP client instance and we avoid sharing it with anything else in the shim. Fixes #2364 Signed-off-by: Samuel Ortiz <samuel.e.ortiz@protonmail.com>
- Loading branch information