[bitnami/opensearch] Fix dashboards liveness probe timeouts (#18450)

* fix(opensearch): increase dashboards probes timeout

Signed-off-by: Alberto Otero Lorenzo <lorenzoa@vmware.com>

* fix(opensearch): improve dashboards probes timeout

Signed-off-by: Alberto Otero Lorenzo <lorenzoa@vmware.com>

* fix(opensearch): bump patch

Signed-off-by: Alberto Otero Lorenzo <lorenzoa@vmware.com>

* Update README.md with readme-generator-for-helm

Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>

---------

Signed-off-by: Alberto Otero Lorenzo <lorenzoa@vmware.com>
Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
Co-authored-by: Bitnami Containers <bitnami-bot@vmware.com>
This commit is contained in:
Alberto Otero
2023-08-16 12:18:40 +02:00
committed by GitHub
parent 42917bb40f
commit 25c89a49a4
3 changed files with 7 additions and 7 deletions

View File

@@ -30,4 +30,4 @@ maintainers:
name: opensearch
sources:
- https://github.com/bitnami/charts/tree/main/bitnami/opensearch
version: 0.1.2
version: 0.1.3

View File

@@ -679,11 +679,11 @@ helm delete --purge my-release
| `dashboards.startupProbe.successThreshold` | Minimum consecutive successes for the probe to be considered successful after having failed (data nodes pod) | `1` |
| `dashboards.startupProbe.failureThreshold` | Minimum consecutive failures for the probe to be considered failed after having succeeded | `5` |
| `dashboards.livenessProbe.enabled` | Enable/disable the liveness probe (data nodes pod) | `true` |
| `dashboards.livenessProbe.initialDelaySeconds` | Delay before liveness probe is initiated (data nodes pod) | `120` |
| `dashboards.livenessProbe.periodSeconds` | How often to perform the probe (data nodes pod) | `10` |
| `dashboards.livenessProbe.initialDelaySeconds` | Delay before liveness probe is initiated (data nodes pod) | `180` |
| `dashboards.livenessProbe.periodSeconds` | How often to perform the probe (data nodes pod) | `20` |
| `dashboards.livenessProbe.timeoutSeconds` | When the probe times out (data nodes pod) | `5` |
| `dashboards.livenessProbe.successThreshold` | Minimum consecutive successes for the probe to be considered successful after having failed (data nodes pod) | `1` |
| `dashboards.livenessProbe.failureThreshold` | Minimum consecutive failures for the probe to be considered failed after having succeeded | `5` |
| `dashboards.livenessProbe.failureThreshold` | Minimum consecutive failures for the probe to be considered failed after having succeeded | `8` |
| `dashboards.readinessProbe.enabled` | Enable/disable the readiness probe (data nodes pod) | `true` |
| `dashboards.readinessProbe.initialDelaySeconds` | Delay before readiness probe is initiated (data nodes pod) | `120` |
| `dashboards.readinessProbe.periodSeconds` | How often to perform the probe (data nodes pod) | `10` |

View File

@@ -2503,11 +2503,11 @@ dashboards:
##
livenessProbe:
enabled: true
initialDelaySeconds: 120
periodSeconds: 10
initialDelaySeconds: 180
periodSeconds: 20
timeoutSeconds: 5
successThreshold: 1
failureThreshold: 5
failureThreshold: 8
## @param dashboards.readinessProbe.enabled Enable/disable the readiness probe (data nodes pod)
## @param dashboards.readinessProbe.initialDelaySeconds Delay before readiness probe is initiated (data nodes pod)
## @param dashboards.readinessProbe.periodSeconds How often to perform the probe (data nodes pod)