[BUG] The default shard and replica settings will cause issues with single-node cluster

[aakruno]

BEFORE CREATING THE ISSUE, CHECK THE FOLLOWING GUIDES:

• FAQ
• Troubleshooting
• Search current/closed issues for similar questions, and utilize github/google search to see if an answer exists for the error I'm encountering.

If the above did not answer your question, proceed with creating an issue below:

Describe the bug

Using LME out of the box, seems to be causing a lot of indices stuck in the "warning" (yellow). There are little to no details as to why this error pops up and help and documentation for ELK and LME have not been a lot of help.

This can, at times, cause the Index Lifecycle Management to not work, stopping rollover to another phase.

A fix to this is to set the replicas to 0.

This seems to be due to being a single-node cluster, as it does not have the means to create a replica.

I previously had a discussion regarding other issues that this caused here: #695

I did this by, replacing index with the affected indexes.

PUT /index/_settings
{
  "index": {
    "number_of_replicas": 0
  }
}

I apologise if you've preferred this as a discussion but figured it was important enough to create an issue for.

To Reproduce

I can seemingly reproduce this by:

1. Install LME
2. Add data to it, I use elastic agents
3. Check up on Index Management and see that a lot of the indices are in a warning state

Please complete the following information

Desktop:

• OS: Windows 11
• Browser: Firefox 142.1

Server:

• OS: Ubuntu 24.04.2 LTS
• Software version: LME 2.1.1

Expected behavior

Indices in green (healthy) under Index Management

[aarz-snl]

This has been identified and should be worked into our latest release -- i have passed this along for tracking