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

Add stack compatibility info to Fleet Server docs #731

Merged
merged 3 commits into from
May 27, 2021
Merged
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 10 additions & 5 deletions docs/en/ingest-management/fleet/fleet-server.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -38,18 +38,23 @@ details, refer to <<fleet-server-deployment>>.

[discrete]
[[fleet-server-compatibility]]
== Compatibility
== Compatibility and prerequisites

{fleet-server} is compatible with the following Elastic products:

* {stack} 7.13 or later (our {ess-product}[hosted {ess}] on {ecloud} or
* {stack} 7.13 or later ({ess-product}[hosted {ess}] on {ecloud}, or
a self-managed cluster).
** For version compatibility: {es} >= {fleet-server} >= {agent} (except for
bugfix releases)
** {kib} should be on the same minor version as {es}.

* {ece} 2.10 or later
** Requires additional wildcard domains and certificates (which normally only
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@simitt @AlexP-Elastic Could you double check this?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should this link to the ECE 2.10 docs which should have more details? I'm not sure it's actionable enough as it stands

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, when the docs are available.

cover *.cname, not ..cname). This enables us to provide the URL for
{fleet-server} of `https://.fleet.`
** The deployment template must contain a slider for APM & Fleet.

//TODO: Confirm that ECE version shown here is correct ^^.

{fleet-server} is supported on x64 architectures only.
//QUESTION: Should this say 2.9? 2.10 is not available yet.
dedemorton marked this conversation as resolved.
Show resolved Hide resolved

[discrete]
[[add-fleet-server]]
Expand Down