-
Notifications
You must be signed in to change notification settings - Fork 69
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add docs for Fleet Server with multiple ES hosts (#1034)
- Loading branch information
Showing
2 changed files
with
14 additions
and
0 deletions.
There are no files selected for viewing
12 changes: 12 additions & 0 deletions
12
docs/en/ingest-management/fleet/fleet-server-multiple-hosts.asciidoc
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,12 @@ | ||
[[fleet-server-multiple-hosts]] | ||
= {fleet-server} with multiple Elasticsearch hosts | ||
|
||
{fleet-server} normally expects the Elasticsearch host that it enrolled with during installation to be available. In the event that that host becomes unavailable, other configured Elasticsearch hosts can be used, but with a few assumptions and restrictions: | ||
|
||
. The Elasticsearch host URL that is used to enroll a new {fleet-server} will never be removed from the {fleet-server} configuration. | ||
|
||
. In order for the output settings that {fleet-server} retrieves from the {fleet-server} policy to be considered valid, {fleet-server} must be able to connect to at least one of the hosts specified in the policy. | ||
|
||
. {fleet-server} gives precedence to attributes from the {fleet-server} policy when it is available. For example, if the flag `--fleet-server-es-ca` is used when {fleet-server} enrolls, and the output that {fleet-server} is currently using contains the flag `ssl.certificate_authorities`, {fleet-server} will attempt to use `ssl.certificate_authorities` as the authentication setting. If the output does not contain `ssl.certificate_authorities` then the value from when {fleet-server} initially enrolled is used. | ||
+ | ||
This behavior can cause issues when the agent in which {fleet-server} is running restarts or is upgraded. Settings that are specified in the {fleet-server} policy that were not used used during the agent's enrollment are lost when the agent restarts. To avoid issues, make sure that the settings used when the {fleet-server} instance first enrolled are always valid. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters