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.

Sign up for GitHub

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

Jump to bottom

[8.15] [DOCS] Update Fleet Server guide - Fleet Server keeps using the ES host provided at install/enroll time. (backport #1185) #1186

Merged
merged 1 commit into from
Jul 18, 2024
Merged

[8.15] [DOCS] Update Fleet Server guide - Fleet Server keeps using the ES host provided at install/enroll time. (backport #1185) #1186

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions docs/en/ingest-management/fleet/add-fleet-server-on-prem.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -212,6 +212,9 @@ token for each {fleet-server}. For other ways to generate service tokens, refer
`--fleet-server-port` options in the `elastic-agent install` command. Refer to the
{fleet-guide}/elastic-agent-cmd-options.html#elastic-agent-install-command[install command documentation]
for details.
* Please note that {fleet-server} will keep using the {es} host provided via `--fleet-server-host` at install time.
The {es} hosts configured in the associated policy will be ignored by the {fleet-server} integration.
We strongly recommend using a load balancer to avoid coupling the {fleet-server} to the provided host.
====
+
At the *Install Fleet Server to a centralized host* step,
Expand Down