Switch fleet's built-in ILM policies to use .actions.rollover.max_primary_shard_size #99983
Labels
:Data Management/ILM+SLM
Index and Snapshot lifecycle management
>enhancement
Team:Data Management
Meta label for data/management team
Description
In the Kibana UI, when looking at ILM policies related to fleet, I see warnings:
Maximum index size is deprecated and will be removed in a future version. Use maximum primary shard size instead.
To avoid confusion for the end-user, I recommend that the same changes which were done in elasticsearch's default ILM policies be done for fleet:
Related to:
The text was updated successfully, but these errors were encountered: