Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[8.15] [DOCS] Update Fleet Server guide - Fleet Server keeps using the ES host provided at install/enroll time. (backport #1185) #1186

Merged
merged 1 commit into from
Jul 18, 2024

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Jul 18, 2024

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.

…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)
@mergify mergify bot requested a review from a team as a code owner July 18, 2024 14:55
@mergify mergify bot added the backport label Jul 18, 2024
Copy link

A documentation preview will be available soon.

Request a new doc build by commenting
  • Rebuild this PR: run docs-build
  • Rebuild this PR and all Elastic docs: run docs-build rebuild

run docs-build is much faster than run docs-build rebuild. A rebuild should only be needed in rare situations.

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 kilfoyle merged commit 4db8f5b into 8.15 Jul 18, 2024
4 checks passed
@mergify mergify bot deleted the mergify/bp/8.15/pr-1185 branch July 18, 2024 15:29
@lucabelluccini
Copy link
Contributor

I think starting branch 8.15 or later, this is no more true following elastic/fleet-server#3464

@kilfoyle
Copy link
Contributor

kilfoyle commented Aug 2, 2024

I think starting branch 8.15 or later, this is no more true following elastic/fleet-server#3464

Thanks @lucabelluccini! I've opened up this PR to remove the warning from the 8.15 docs and later docs: #1219

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants