[REQUEST]: Document how to install Fleet Server on premise in High available setup

lucabelluccini commented 1 year ago

Description

We need a tutorial-like guide on how to install Fleet Servers on-premise being high available.

Recommend using a reverse proxy/load balancer (e.g. fleet.mycomp.com) and recommend best values for timeouts for long polling for Elastic Agents
Setup the Fleet Server Host in Fleet UI to match the same DNS of the reverse proxy (e.g. fleet.mycomp.com)
Make sure the certificates validate against the DNS and IP of both the Fleet Server 1 (e.g. fleet1.mycompo.com) and the reverse proxy hostname (e.g. fleet.mycomp.com)
Enroll the first Fleet Server (e.g. fleet1.mycomp.com)
Enroll the second Fleet Server (e.g. fleet2.mycomp.com)

To test out, enroll an Elastic Agent against fleet.mycomp.com.

This could even expanded further to suggest to use a reverse proxy/load balancer in front of multiple Kibana instances.

Resources

We have no guidance on this except https://www.elastic.co/guide/en/fleet/current/add-fleet-server-on-prem.html

Collaboration

TBD. The docs and product team will work together to determine the best path forward.

Point of contact.

Main contact: @lucabelluccini discussed with @pierrehilbert / @jlind23 in last weekly

@lucabelluccini might try out the setup steps and share them with the doc/eng team, but it will be on doc team to write the actual documentation.

nimarezainia commented 1 year ago

@lucabelluccini could you help me understand the priority of this? I know it's important to have, just wondering if there's been a widespread request for this use case. thx.

lucabelluccini commented 1 year ago

Enterprise users are requesting how to setup their own Fleet Server in a similar way as we do for Elastic Cloud. I do not have a metric to track this right now but it's likely additional enhancements will be associated to this issue from now on.

lucabelluccini commented 8 months ago

Correlated enhancement would be:

1) As a user, I want to be able to create a Fleet Server policy (APIs) and deploy the Fleet Server via CLI without interacting with Kibana Fleet UI (all the steps should be reduced to CLI). This is important for enterprise users who want to automate processes.

Right now, it should be possible, but:

One needs to follow once the Fleet wizard and have a running Kibana
- We should have the step-by-step process in the documentation without the need of Kibana
Not all the steps have their CLI/API counterpart (example: "how to create a service account key" has no associated curl/api version in Fleet, but it should be possible to use https://www.elastic.co/guide/en/elasticsearch/reference/current/service-accounts.html)

2) Same as above, but for an Elastic Agent

Let me know if this should be a separate issue or we can reuse this one.

kilfoyle commented 8 months ago

Thanks for the extra information @lucabelluccini! I'm not sure how soon I can get to this (it's part of a large docs backlog) but I'll do my best. Having both parts in the same issue is okay.

lucabelluccini commented 2 months ago

If we're going to publish a tutorial or an extended guide, we should include the warning I'm suggesting at https://github.com/elastic/ingest-docs/pull/1185

kilfoyle commented 2 months ago

@jlind23 @ycombinator For this issue I'd need someone from development to provide info or some form of draft.

We do have this internal Running a local Fleet Server and enrolling Elastic Agents document that perhaps could be a basis for docs, but it doesn't have the high availability info.

@nimarezainia Perhaps this guide would be a nice way to fill the "installling Fleet Server" space in the docs that we've discussed.

jlind23 commented 2 months ago

@michel-laterman or @nchaulet would most probably be the best fit here.

ycombinator commented 2 months ago

@jlind23 @ycombinator For this issue I'd need someone from development to provide info or some form of draft.

@michel-laterman should be able to help with this. I will add it to one of his upcoming sprints.

elastic / ingest-docs