Is your feature request related to a problem? Please describe.
Sometimes service can loose connectivity to database and it needs to have a possibility to check this event and restart service to reconnect it to DB.
We have faced with this situation during GCP Managed SQL maintenance window when switching to active base can take about 30 seconds.
Describe the solution you'd like
Liveness Probe like we have below can help us to identify problem and resolve it automatically, but we can't set this custom probe with helm values. It is not supported with current Helm chart.
exec:
command:
- /bin/sh
- -c
- tctl --tls_cert_path /etc/temporal/config/certs/cluster.pem --tls_key_path
/etc/temporal/config/certs/cluster.key --tls_ca_path /etc/temporal/config/certs/ca.cert
n l
failureThreshold: 3
initialDelaySeconds: 150
periodSeconds: 20
successThreshold: 1
timeoutSeconds: 10
Please add a possibility to rewrite default livenessProbe configuration via custom Helm values.
Is your feature request related to a problem? Please describe.
Sometimes service can loose connectivity to database and it needs to have a possibility to check this event and restart service to reconnect it to DB.
We have faced with this situation during GCP Managed SQL maintenance window when switching to active base can take about 30 seconds.
Describe the solution you'd like
Liveness Probe like we have below can help us to identify problem and resolve it automatically, but we can't set this custom probe with helm values. It is not supported with current Helm chart.
Please add a possibility to rewrite default livenessProbe configuration via custom Helm values.