From a156a43224214269f1f26075119a36b2a2870d3c Mon Sep 17 00:00:00 2001 From: Michael Morello Date: Wed, 26 Mar 2025 11:32:58 +0100 Subject: [PATCH 1/3] Describe limitation of some unsupported Elasticsearch configurations --- .../deploy/cloud-on-k8s/node-configuration.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/deploy-manage/deploy/cloud-on-k8s/node-configuration.md b/deploy-manage/deploy/cloud-on-k8s/node-configuration.md index ddd7e5064c..a8f5746bac 100644 --- a/deploy-manage/deploy/cloud-on-k8s/node-configuration.md +++ b/deploy-manage/deploy/cloud-on-k8s/node-configuration.md @@ -34,5 +34,19 @@ spec: node.roles: ["data", "ingest", "ml", "transform"] ``` +::::{warning} +ECK parses Elasticsearch configuration and normalizes it to YAML. Consequently, some Elasticsearch configuration schema are impossible to express with ECK and, therefore, must be set using https://www.elastic.co/guide/en/elasticsearch/reference/current/settings.html#cluster-setting-types[dynamic cluster settings]. For example: +```yaml +spec: + nodeSets: + - name: data + # ... + config: + cluster.max_shards_per_node: 1000 + cluster.max_shards_per_node.frozen: 1000 # <= This won't work because cluster.max_shards_per_node is defined as a scalar value on the previous line + # ... +``` +:::: + For more information on Elasticsearch settings, check [Configuring Elasticsearch](/deploy-manage/deploy/self-managed/configure-elasticsearch.md). From 9a3299acc32348b4297c21f3aadaa79dd53b60d5 Mon Sep 17 00:00:00 2001 From: Michael Morello Date: Wed, 26 Mar 2025 11:39:09 +0100 Subject: [PATCH 2/3] Fix link --- deploy-manage/deploy/cloud-on-k8s/node-configuration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deploy-manage/deploy/cloud-on-k8s/node-configuration.md b/deploy-manage/deploy/cloud-on-k8s/node-configuration.md index a8f5746bac..08cbd8a06d 100644 --- a/deploy-manage/deploy/cloud-on-k8s/node-configuration.md +++ b/deploy-manage/deploy/cloud-on-k8s/node-configuration.md @@ -35,7 +35,7 @@ spec: ``` ::::{warning} -ECK parses Elasticsearch configuration and normalizes it to YAML. Consequently, some Elasticsearch configuration schema are impossible to express with ECK and, therefore, must be set using https://www.elastic.co/guide/en/elasticsearch/reference/current/settings.html#cluster-setting-types[dynamic cluster settings]. For example: +ECK parses Elasticsearch configuration and normalizes it to YAML. Consequently, some Elasticsearch configuration schema are impossible to express with ECK and, therefore, must be set using [dynamic cluster settings](/deploy-manage/deploy/self-managed/configure-elasticsearch.md#cluster-setting-types). For example: ```yaml spec: nodeSets: From 4278625b8af3d95a5dd145b5d59e888d6abf8ce9 Mon Sep 17 00:00:00 2001 From: Michael Morello Date: Wed, 26 Mar 2025 11:52:03 +0100 Subject: [PATCH 3/3] Update note --- deploy-manage/deploy/cloud-on-k8s/node-configuration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deploy-manage/deploy/cloud-on-k8s/node-configuration.md b/deploy-manage/deploy/cloud-on-k8s/node-configuration.md index 08cbd8a06d..11262c3881 100644 --- a/deploy-manage/deploy/cloud-on-k8s/node-configuration.md +++ b/deploy-manage/deploy/cloud-on-k8s/node-configuration.md @@ -43,7 +43,7 @@ spec: # ... config: cluster.max_shards_per_node: 1000 - cluster.max_shards_per_node.frozen: 1000 # <= This won't work because cluster.max_shards_per_node is defined as a scalar value on the previous line + cluster.max_shards_per_node.frozen: 1000 # This won't work because cluster.max_shards_per_node is defined as a scalar value on the previous line # ... ``` ::::