Open
Description
Context: [REQUEST]: Serverless clarification for how agents get updated
TL;DR: Elastic Agents used with a Serverless project are not upgraded automatically. The user must take care of the upgrade of the Elastic Agents, and they can do it at their own convenience.
I've identified a couple of deploy-manage docs that could get a clarification based on that information:
- Upgrade your deployment or cluster: This includes a short sentence about Serverless being automatically upgraded, but it could probably use a note that (self-hosted) Elastic ingest components must be upgraded by the user.
- Upgrade your ingest components: Are Elastic Agent, Logstash and Beats self-hosted in all use cases? If we can safely say that 99% of the time they are, would it make sense to add Serverless to the
applies_toin this doc, and try to figure out a different wording? Right now this doc is part of a user workflow for upgrading a deployment/cluster (other upgrade docs mention this one as their last step, e.g., Upgrade on ECH, Upgrade on ECK), but if this doc applies to Serverless too, we need to figure out how to adjust this doc to fit the Serverless use case. - Answers to common serverless questions: We could add a Q&A here for this particular issue.
- Architectural differences and Compare Elastic Cloud Hosted and Serverless: For these two I am not entirely sure as they compare ECH and Serverless, and ingest components are separate from those, but I wonder if it makes sense to add a note somewhere that self-hosted Elastic ingest components are managed by the user in Serverless projects?