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

List ports and routes required for Stack deployment #2431

Open
jrodewig opened this issue Jun 8, 2023 · 10 comments
Open

List ports and routes required for Stack deployment #2431

jrodewig opened this issue Jun 8, 2023 · 10 comments
Assignees

Comments

@jrodewig
Copy link
Contributor

jrodewig commented Jun 8, 2023

Problem
Users need to understand which ports and network routes need to be available to design a Stack deployment. Right now, this information is scattered across several Stack guides.

@liladler
Copy link

liladler commented Jun 8, 2023

Thanks for this @jrodewig.

It'd be great to have this documented so open source & paying customers would have a centralised starting point, as they'd be able to self serve.
A crucial point to this as well would be a reference architecture, combining all of our components (beats/agent/kibana/fleet/es etc)

@jhmass
Copy link

jhmass commented Jun 8, 2023

This has been requested quite often. It would be great if this was available. Please also include ports related to orchestration features like ECE and ECK. Where appropriate?

Thanks!

@Ian7890
Copy link

Ian7890 commented Jun 8, 2023

I agree, this is a really obvious gap in the Elastic.co documentation that I would expect to be in any enterprise applications documentation set.

I was in conversation with Lily this week on this topic and she agreed to raise it internally, it seems that I am just the latest in a line of people requesting this :-)

@sm2206
Copy link

sm2206 commented Jun 9, 2023

I have also been trying to find this information, if it were provided on a single page it would be a massive help for beginners taking on new installations.

@jamesagarside
Copy link

Glad to see this. It will seriously speed up the journey for people evaluating Elastic.

@liladler
Copy link

liladler commented Aug 2, 2023

@jrodewig hi, is there any update on this?
This is still being asked for by users & customers and would be great to be able to share a centralised view on our architecture.

@karenzone
Copy link
Contributor

karenzone commented Aug 2, 2023

This is not the destination, but is a start: elastic/ingest-docs#197 and elastic/ingest-docs#390.
Docs here: https://www.elastic.co/guide/en/ingest/current/agent-installed.html

@jrodewig
Copy link
Contributor Author

jrodewig commented Aug 2, 2023

Hi @liladler!

Sharing details from our offline convo: This is in our backlog, but we've got some other important work that's prioritized ahead of it. I can't guarantee a publish date, but we'll try to fit it in soon.

Thanks again for raising this. Please continue to surface requests like this to the docs team. It's really valuable.

@jrodewig
Copy link
Contributor Author

jrodewig commented Aug 24, 2023

I opened #2531 as a stopgap to cover ports for major Elastic Stack components. We'll need to do some follow-up PRs to cover ECE/ECK ports as well as linking to the settings. However, I think this is better than nothing for now.

@karenzone can work on a more exhaustive update once our priorities clear up.

@jrodewig
Copy link
Contributor Author

Some feedback from #2531:

Ingest architectures

  • The reference architecture focuses on ingest so only shows breakdown of ingest components. Would be great to have a reference architecture that presents Elasticsearch components, such as ML nodes, Hot, Cold, Frozen buckets etc.

Cloud

  • The page references APM/fleet server. In the Cloud console we still call it integration server. might worth a clarification that it refers to the same component?
  • We're referencing cloud, but cloud ports are different (uses TLS).

These were out of scope for the PR, but we should look to address them later on.

jrodewig added a commit that referenced this issue Aug 30, 2023
Documents the default ports for major Elastic Stack components.

Rel: #2431
mergify bot pushed a commit that referenced this issue Aug 30, 2023
Documents the default ports for major Elastic Stack components.

Rel: #2431
(cherry picked from commit bc27017)
@jrodewig jrodewig removed their assignment Aug 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants