Enrollment handling for containerized agents
Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability This functionality is generally available and ready for production usage. Serverless interfaces and procedures might differ from classic Elastic Stack deployments. The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability This functionality is generally available and ready for production usage. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
Serverless
Generally available
Stack
Generally available
For Fleet-managed Elastic Agents that run in a containerized environment (including Docker, Kubernetes, and others), enrollment handling is managed as follows:
- Enrollment Verification: Elastic Agent checks the stored enrollment conditions within its container environment and re-enrolls only when necessary.
- Unenrollment Handling: If an Elastic Agent is unenrolled through the Fleet UI but still references a valid enrollment token provided through environment variables, it will automatically re-enroll on the next container restart.
In versions lower than 8.18, an unenrolled agent remains unenrolled and does not re-enroll, even if a valid enrollment token is still available.