Migrate from using port to use named pipes or socketfile #218
Labels
8.5-candidate
Team:Elastic-Agent-Control-Plane
Label for the Agent Control Plane team
V2-Architecture
The v1 protocol that we have today works over TCP port, with a higher quantity of services to be run by the Elastic Agent this will not scale easily and can cause conflict for already used port.
We should migrate our connection strategy to:
The text was updated successfully, but these errors were encountered: