[8.14] [DOCS] Update Fleet Server guide - Fleet Server keeps using the ES host provided at install/enroll time. (backport #1185) #1187
Conversation
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
![mergify[bot]](https://avatars.githubusercontent.com/in/10562?s=60&v=4){kind=small}
…st provided at install/enroll time. (#1185) * [DOCS] Update Fleet Server guide * Update docs/en/ingest-management/fleet/add-fleet-server-on-prem.asciidoc * Update docs/en/ingest-management/fleet/add-fleet-server-on-prem.asciidoc Co-authored-by: Karen Metts <[email protected]> --------- Co-authored-by: David Kilfoyle <[email protected]> Co-authored-by: Karen Metts <[email protected]> (cherry picked from commit 7257560)
|
A documentation preview will be available soon. Request a new doc build by commenting
If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here. |
kilfoyle
approved these changes
Jul 18, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Feedback from real users.
Due to the limitation elastic/elastic-agent#2784 (https://support.elastic.co/knowledge/f69b6e46), Fleet Server still keeps using the Elasticsearch host provided at enroll time instead of using the one in the policy.
Elastic agent & Fleet are working on overcoming the limitation via elastic/fleet-server#3464 but we should add a big warning message about this.
This message should be backported to all versions, at least until we'll introduce the enhancements to take into account the ES hosts coming from the policy.
This is an automatic backport of pull request #1185 done by Mergify.