Liveness probe

camundaenthu · October 31, 2023, 11:51pm

Hello,

We deploy the camunda-platform helm chart 8.2.8. We noticed that the readiness probe is enabled by default but the liveness probe is not. Just curious, why the liveness probe is not enabled by default? Anything we need to be aware of if we choose to enable it? We would like to enable the liveness probe for both camunda-zeebe-gateway and camunda-zeebe.

We noticed in our k8s cluster that although the gateway and zeebe pods show Running they do not respond and we see the ‘GRPC usage exception – channel closed’ in our client (using pyzeebe to access zeebe). We have to manually restart zeebe and gateway pods.

We hope that if we enable the liveness probe, k8s will restart zeebe gateway and zeebe when the probes fail so we don’t run into the issue we did earlier.

Appreciate any feedback.

nathan.loding · November 3, 2023, 1:51pm

Hi @camundaenthu - I thought the liveness probes were enabled by default … I’ll have to double check this. I am not aware of anything you need to be aware when enabling the probes. You can find the documentation here: Gateway health probes | Camunda 8 Docs

camundaenthu · November 3, 2023, 4:12pm

Thanks @nathan.loding

This is what I was referring to:

Zeebe section

Zeebe gateway section

github.com

camunda/camunda-platform-helm/blob/a2584a845908e05e982f86e7855b5c98a4f1355b/charts/camunda-platform/values.yaml

# Default values for Camunda Helm chart.
# This is a YAML-formatted file.
# Declare variables to be passed into your templates.

# The values file follows helm best practices https://helm.sh/docs/chart_best_practices/values/
#
# This means:
#   * Variable names should begin with a lowercase letter, and words should be separated with camelcase.
#   * Every defined property in values.yaml should be documented. The documentation string should begin with the name of the property that it describes, and then give at least a one-sentence description
#
# Furthermore, we try to apply the following pattern: # [VarName] [conjunction] [definition]
#
# VarName:
#
#  * In the documentation the variable name is started with a big letter, similar to kubernetes resource documentation.
#  * If the variable is part of a subsection/object we use a json path expression (to make it more clear where the variable belongs to).
#    The root (chart name) is omitted (e.g. zeebe). This is useful for using --set in helm.
#
# Conjunction:
#   * [defines] for mandatory configuration

This file has been truncated. show original