Skip to content

Commit 72c223e

Browse files
Add clarification about Elastic Agent upgrade on Serverless (#1720)
Added a clarification that Elastic Agents are not upgraded automatically ## Issue Closes [#1792](elastic/ingest-docs#1792) ## Preview https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/1720/reference/fleet/fleet-agent-serverless-restrictions
1 parent 9a0753a commit 72c223e

File tree

1 file changed

+8
-3
lines changed

1 file changed

+8
-3
lines changed

reference/fleet/fleet-agent-serverless-restrictions.md

Lines changed: 8 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -18,10 +18,15 @@ If you are using {{agent}} with [{{serverless-full}}](/deploy-manage/deploy/elas
1818
* The number of {{agents}} that may be connected to an {{serverless-full}} project is limited to 10 thousand.
1919
* The minimum supported version of {{agent}} supported for use with {{serverless-full}} is 8.11.0.
2020

21-
$$$outputs-serverless-restrictions$$$
22-
**Outputs**
21+
### Outputs
2322

24-
* On {{serverless-short}}, you can configure new {{es}} outputs to use a proxy, with the restriction that the output URL is fixed. Any new {{es}} outputs must use the default {{es}} host URL.
23+
On {{serverless-short}}, you can configure new {{es}} outputs to use a proxy, with the restriction that the output URL is fixed. Any new {{es}} outputs must use the default {{es}} host URL.
24+
25+
### Upgrade
26+
27+
{{agents}} are not automatically upgraded with the upgrade of the {{serverless-short}} project. You can upgrade standalone or {{fleet}}-managed {{agent}}s at your convenience.
28+
29+
For more information, see [](upgrade-elastic-agent.md) and [](upgrade-standalone.md).
2530

2631

2732
## {{fleet}} [fleet-serverless-restrictions]

0 commit comments

Comments
 (0)