Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate from using port to use named pipes or socketfile #218

Closed
Tracked by #189
ph opened this issue Mar 17, 2022 · 1 comment
Closed
Tracked by #189

Migrate from using port to use named pipes or socketfile #218

ph opened this issue Mar 17, 2022 · 1 comment
Labels

Comments

@ph
Copy link
Contributor

ph commented Mar 17, 2022

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:

  • Named pipe under Windows
  • Sockerfile for macOS and Linux
@ph ph added the Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team label Mar 17, 2022
@ph ph changed the title Migrate from using port to use named pipes or socketfile instead of ports. Migrate from using port to use named pipes or socketfile instead of ports Mar 17, 2022
@ph ph changed the title Migrate from using port to use named pipes or socketfile instead of ports Migrate from using port to use named pipes or socketfile Mar 17, 2022
@jlind23
Copy link
Contributor

jlind23 commented May 27, 2024

Closing this as a duplicated of #3998

@jlind23 jlind23 closed this as not planned Won't fix, can't repro, duplicate, stale May 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants