You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: bitnami/elasticsearch/README.md
+13Lines changed: 13 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -140,6 +140,9 @@ The following table lists the configurable parameters of the Elasticsearch chart
140
140
|`master.readinessProbe.timeoutSeconds`| When the probe times out (master-eligible nodes pod) |`5`|
141
141
|`master.readinessProbe.successThreshold`| Minimum consecutive successes for the probe to be considered successful after having failed (master-eligible nodes pod) |`1`|
142
142
|`master.readinessProbe.failureThreshold`| Minimum consecutive failures for the probe to be considered failed after having succeeded |`5`|
|`master.serviceAccount.create`| Enable creation of ServiceAccount for the master node |`false`|
144
147
|`master.serviceAccount.name`| Name of the created serviceAccount | Generated using the `elasticsearch.master.fullname` template |
145
148
|`master.autoscaling.enabled`| Enable autoscaling for master replicas |`false`|
@@ -193,13 +196,17 @@ The following table lists the configurable parameters of the Elasticsearch chart
193
196
|`coordinating.readinessProbe.timeoutSeconds`| When the probe times out (coordinating-only nodes pod) |`5`|
194
197
|`coordinating.readinessProbe.successThreshold`| Minimum consecutive successes for the probe to be considered successful after having failed (coordinating-only nodes pod) |`1`|
195
198
|`coordinating.readinessProbe.failureThreshold`| Minimum consecutive failures for the probe to be considered failed after having succeeded |`5`|
|`coordinating.serviceAccount.create`| Enable creation of ServiceAccount for the coordinating-only node |`false`|
197
203
|`coordinating.serviceAccount.name`| Name of the created serviceAccount | Generated using the `elasticsearch.coordinating.fullname`|
198
204
|`coordinating.autoscaling.enabled`| Enable autoscaling for coordinating replicas |`false`|
199
205
|`coordinating.autoscaling.minReplicas`| Minimum number of coordinating replicas |`2`|
200
206
|`coordinating.autoscaling.maxReplicas`| Maximum number of coordinating replicas |`11`|
201
207
|`coordinating.autoscaling.targetCPU`| Target CPU utilization percentage for coordinating replica autoscaling |`nil`|
202
208
|`coordinating.autoscaling.targetMemory`| Target Memory utilization percentage for coordinating replica autoscaling |`nil`|
209
+
203
210
### Data parameters
204
211
205
212
| Parameter | Description | Default |
@@ -235,6 +242,9 @@ The following table lists the configurable parameters of the Elasticsearch chart
235
242
|`data.livenessProbe.timeoutSeconds`| When the probe times out (data nodes pod) |`5`|
236
243
|`data.livenessProbe.successThreshold`| Minimum consecutive successes for the probe to be considered successful after having failed (data nodes pod) |`1`|
237
244
|`data.livenessProbe.failureThreshold`| Minimum consecutive failures for the probe to be considered failed after having succeeded |`5`|
|`data.podAnnotations`| Annotations for data pods. |`{}`|
239
249
|`data.podAffinityPreset`| Data Pod affinity preset. Ignored if `affinity` is set. Allowed values: `soft` or `hard`|`""`|
240
250
|`data.podAntiAffinityPreset`| Data Pod anti-affinity preset. Ignored if `affinity` is set. Allowed values: `soft` or `hard`|`soft`|
@@ -289,6 +299,9 @@ The following table lists the configurable parameters of the Elasticsearch chart
289
299
|`ingest.livenessProbe.timeoutSeconds`| When the probe times out (ingest nodes pod) |`5`|
290
300
|`ingest.livenessProbe.successThreshold`| Minimum consecutive successes for the probe to be considered successful after having failed (ingest nodes pod) |`1`|
291
301
|`ingest.livenessProbe.failureThreshold`| Minimum consecutive failures for the probe to be considered failed after having succeeded |`5`|
0 commit comments