Yellow cluster status on single-node fresh install

[AlexRuiz7]

Description

On a fresh single-node installation, the cluster status returns yellow as the .opendistro-job-scheduler-lock has 1 replica index. This internal system index is used to store the ISM plugin configuration. The index is being created after the rollover + alias policy creation.

GET _cat/indices?v

health status index                                uuid                   pri rep docs.count docs.deleted store.size pri.store.size
yellow open   .opendistro-job-scheduler-lock       Ve6UDa-bTweSJdyauRdVBA   1   1          2            2     17.7kb  

GET _cluster/health?pretty

{
  "cluster_name" : "wazuh-cluster",
  "status" : "yellow",
  "timed_out" : false,
  "number_of_nodes" : 1,
  "number_of_data_nodes" : 1,
  "discovered_master" : true,
  "discovered_cluster_manager" : true,
  "active_primary_shards" : 11,
  "active_shards" : 11,
  "relocating_shards" : 0,
  "initializing_shards" : 0,
  "unassigned_shards" : 1,
  "delayed_unassigned_shards" : 0,
  "number_of_pending_tasks" : 0,
  "number_of_in_flight_fetch" : 0,
  "task_max_waiting_in_queue_millis" : 0,
  "active_shards_percent_as_number" : 91.66666666666666
}

[AlexRuiz7]

I asked to OpenSearch how can we set the replica count for this system index to 0 before its creation.

The only solution that currently comes to my mind is to set its replica count to 0 in the indexer-ism-init.sh script.

PUT .opendistro-job-scheduler-lock/_settings
{
  "index": {
    "number_of_replicas": 0
  }
}

However, this might not solve the problem, as there may be other internal indices (.opendistro-ism-config) with 1 replica (default value).