Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] There is no way to configure custom livenessProbe for Temporal services #653

Open
Kiseloff opened this issue Feb 25, 2025 · 0 comments · May be fixed by #654
Open

[Feature Request] There is no way to configure custom livenessProbe for Temporal services #653

Kiseloff opened this issue Feb 25, 2025 · 0 comments · May be fixed by #654
Labels
enhancement New feature or request

Comments

@Kiseloff
Copy link

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.

@Kiseloff Kiseloff added the enhancement New feature or request label Feb 25, 2025
Kiseloff pushed a commit to Kiseloff/temporal-helm-charts that referenced this issue Feb 26, 2025
Kiseloff added a commit to Kiseloff/temporal-helm-charts that referenced this issue Feb 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant