From d40e5337c059c32c49f9597365ff59eb565f210e Mon Sep 17 00:00:00 2001
From: David Kilfoyle <41695641+kilfoyle@users.noreply.github.com>
Date: Wed, 7 Aug 2024 13:51:40 -0400
Subject: [PATCH] Remove warning about Fleet Server using ES host at
 install/enroll time (#1219)

---
 .../ingest-management/fleet/add-fleet-server-on-prem.asciidoc  | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/docs/en/ingest-management/fleet/add-fleet-server-on-prem.asciidoc b/docs/en/ingest-management/fleet/add-fleet-server-on-prem.asciidoc
index 8b2c6ee1d..339cacd37 100644
--- a/docs/en/ingest-management/fleet/add-fleet-server-on-prem.asciidoc
+++ b/docs/en/ingest-management/fleet/add-fleet-server-on-prem.asciidoc
@@ -212,9 +212,6 @@ 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,