From 6b51c85225246ca20502a620a8c1a614b62322eb Mon Sep 17 00:00:00 2001 From: nima Date: Tue, 21 Jan 2025 01:48:27 +1100 Subject: [PATCH] Explain why Agent needs to connect to Kibana (#1627) * Explain why Agent needs to connect to Kibana * Update docs/en/ingest-management/fleet/add-fleet-server-on-prem.asciidoc --------- Co-authored-by: David Kilfoyle <41695641+kilfoyle@users.noreply.github.com> (cherry picked from commit bac20b6f52f4a4613af4fd876487fe592ce2ecca) --- .../ingest-management/fleet/add-fleet-server-on-prem.asciidoc | 3 +++ 1 file changed, 3 insertions(+) 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 cd896bbda..07240376a 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 @@ -98,6 +98,9 @@ You may need to allow access to these ports. Refer to the following table for de | {fleet-server} → {es} | 9200 |=== +NOTE: Connectivity to {kib} on port 5601 is optional and not required at all times. {agent} and {fleet-server} may need to connect to {kib} if deployed in a +container environment where an enrollment token can not be provided during deployment. + //[discrete] //[[add-fleet-server-on-prem-hosts]] //= Add {fleet-server} hosts