[bitnami/matomo] Use different liveness/readiness probes (#25976)

Signed-off-by: David Gomez <dgomezleon@vmware.com>
This commit is contained in:
David Gomez
2024-05-20 09:37:14 +02:00
committed by GitHub
parent 0fdb31028c
commit a4e6ed0b86
5 changed files with 6 additions and 14 deletions

View File

@@ -1,9 +1,9 @@
dependencies:
- name: mariadb
repository: oci://registry-1.docker.io/bitnamicharts
version: 18.0.5
version: 18.0.6
- name: common
repository: oci://registry-1.docker.io/bitnamicharts
version: 2.19.2
digest: sha256:c5470e186b8c675df045d2df334629fb8a47a53f87044bd4348c80105ca25eaf
generated: "2024-05-18T01:39:11.597491837Z"
digest: sha256:c47e6893bd32647cb5b1ace19e702087fa6e5301cd7e7b37eae4313afa327e2c
generated: "2024-05-20T09:21:46.519597+02:00"

View File

@@ -39,4 +39,4 @@ maintainers:
name: matomo
sources:
- https://github.com/bitnami/charts/tree/main/bitnami/matomo
version: 7.1.2
version: 7.1.3

View File

@@ -235,7 +235,6 @@ helm install my-release --set persistence.existingClaim=PVC_NAME oci://REGISTRY_
| `startupProbe.failureThreshold` | Failure threshold for startupProbe | `5` |
| `startupProbe.successThreshold` | Success threshold for startupProbe | `1` |
| `livenessProbe.enabled` | Enable livenessProbe | `true` |
| `livenessProbe.path` | Request path for livenessProbe | `/matomo.php` |
| `livenessProbe.initialDelaySeconds` | Initial delay seconds for livenessProbe | `600` |
| `livenessProbe.periodSeconds` | Period seconds for livenessProbe | `10` |
| `livenessProbe.timeoutSeconds` | Timeout seconds for livenessProbe | `5` |

View File

@@ -197,8 +197,7 @@ spec:
livenessProbe: {{- include "common.tplvalues.render" (dict "value" .Values.customLivenessProbe "context" $) | nindent 12 }}
{{- else if .Values.livenessProbe.enabled }}
livenessProbe:
httpGet:
path: {{ .Values.livenessProbe.path }}
tcpSocket:
port: http
initialDelaySeconds: {{ .Values.livenessProbe.initialDelaySeconds }}
periodSeconds: {{ .Values.livenessProbe.periodSeconds }}

View File

@@ -408,13 +408,8 @@ startupProbe:
failureThreshold: 5
successThreshold: 1
## Configure extra options for liveness probe
## Matomo core exposes / to unauthenticated requests, making it a good
## default liveness and readiness path. However, that may not always be the
## case. For example, if the image value is overridden to an image containing a
## module that alters that route, or an image that does not auto-install Matomo.
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/#configure-probes
## @param livenessProbe.enabled Enable livenessProbe
## @param livenessProbe.path Request path for livenessProbe
## @param livenessProbe.initialDelaySeconds Initial delay seconds for livenessProbe
## @param livenessProbe.periodSeconds Period seconds for livenessProbe
## @param livenessProbe.timeoutSeconds Timeout seconds for livenessProbe
@@ -423,7 +418,6 @@ startupProbe:
##
livenessProbe:
enabled: true
path: /matomo.php
initialDelaySeconds: 600
periodSeconds: 10
timeoutSeconds: 5
@@ -431,7 +425,7 @@ livenessProbe:
successThreshold: 1
## Configure extra options for readiness probe
## Matomo core exposes / to unauthenticated requests, making it a good
## default liveness and readiness path. However, that may not always be the
## default startup and readiness path. However, that may not always be the
## case. For example, if the image value is overridden to an image containing a
## module that alters that route, or an image that does not auto-install Matomo.
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/#configure-probes