Limitations of this release
editLimitations of this release
editThis functionality is in technical preview and may be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features.
This experimental release allows you to try out new capabilities. There is no migration path for future releases. You must test in a dedicated cluster. Delete the cluster when you are done. You will not be able to upgrade the cluster.
Ingest Manager is currently only available to users with the superuser role. This role is necessary to create indices, install integration assets, and update Elastic Agent configurations. In order to use Fleet, the Elastic Agents must have a direct network connection to Kibana and Elasticsearch. It is also possible to run the Elastic Agents in standalone mode in cases where a network connection is not available or not needed.
This feature has several additional limitations at the current time:
- Support for only 9 integrations (more coming soon)
- Support for only Filebeat and Metricbeat
- We recommend you enroll no more than 100 Agents
- No output to Logstash, Kafka, or other remote clusters
- No proxy support in Elastic Agent
- Kibana must have internet access to download integration packages
- No support for advanced Beats settings like multiline, processors, and so on
- No custom index templates or pipelines
- No support for Kubernetes or Docker autodiscovery
Experimental releases are not officially supported, but we encourage you to report issues in our discuss forum.