Samuel Ortiz 760ec4e58a 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>

2021-07-30 16:51:01 +02:00

..

agent

Merge pull request #2248 from lifupan/check_file_exist

2021-07-27 23:29:26 +08:00

runtime

virtcontainers: clh: Do not use the default HTTP client

2021-07-30 16:51:01 +02:00

trace-forwarder

docs: Remove table of contents

2021-07-30 10:58:22 +01:00