From cb82f1148d4224b84a27077fdf12f1a2ba7ed379 Mon Sep 17 00:00:00 2001 From: David Kilfoyle <41695641+kilfoyle@users.noreply.github.com> Date: Wed, 24 Apr 2024 14:09:23 -0400 Subject: [PATCH] Revert "Add docs for Fleet Server with multiple ES hosts (#1034)" (#1046) This reverts commit 5dfb174fe41d39ab56158c9b4a356acf6c279b10. (cherry picked from commit ac60278556c60edd70e6dc6be0c6db3c647e7432) --- .../fleet/fleet-server-multiple-hosts.asciidoc | 12 ------------ docs/en/ingest-management/index.asciidoc | 2 -- 2 files changed, 14 deletions(-) delete mode 100644 docs/en/ingest-management/fleet/fleet-server-multiple-hosts.asciidoc diff --git a/docs/en/ingest-management/fleet/fleet-server-multiple-hosts.asciidoc b/docs/en/ingest-management/fleet/fleet-server-multiple-hosts.asciidoc deleted file mode 100644 index 931f1fd8a..000000000 --- a/docs/en/ingest-management/fleet/fleet-server-multiple-hosts.asciidoc +++ /dev/null @@ -1,12 +0,0 @@ -[[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. diff --git a/docs/en/ingest-management/index.asciidoc b/docs/en/ingest-management/index.asciidoc index c8a6ea37d..8adafbfcc 100644 --- a/docs/en/ingest-management/index.asciidoc +++ b/docs/en/ingest-management/index.asciidoc @@ -31,8 +31,6 @@ include::fleet/fleet-server-secrets.asciidoc[leveloffset=+2] include::fleet/fleet-server-monitoring.asciidoc[leveloffset=+2] -include::fleet/fleet-server-multiple-hosts.asciidoc[leveloffset=+2] - include::elastic-agent/install-elastic-agent.asciidoc[leveloffset=+1] include::elastic-agent/install-fleet-managed-elastic-agent.asciidoc[leveloffset=+2]