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

Define a liveness probe for the argo-workflows server #3174

Closed
Julienlin opened this issue Feb 19, 2025 · 0 comments · Fixed by #3175
Closed

Define a liveness probe for the argo-workflows server #3174

Julienlin opened this issue Feb 19, 2025 · 0 comments · Fixed by #3175
Labels
argo-workflows enhancement New feature or request

Comments

@Julienlin
Copy link

Is your feature request related to a problem?

We experienced a case where the argo-workflows server died and was not responding. This could have been fixed easily by a restart from initiated by Kubernetes.

Related helm chart

argo-workflows

Describe the solution you'd like

We would like to have something similar to what the argo-workflows controller has:

          livenessProbe: {{ .Values.server.livenessProbe | toYaml | nindent 12 }}

values.yaml:

  # -- Configure liveness [probe] for the server
  # @default -- See [values.yaml]
  livenessProbe:
    httpGet:
      port: 2746
      path: /
    failureThreshold: 3
    initialDelaySeconds: 90
    periodSeconds: 60
    timeoutSeconds: 30

Describe alternatives you've considered

No response

Additional context

It comes to our attention that the argo workflow server does not provide a health check endpoint (see argoproj/argo-workflows#7066). But we could use the same endpoint as the readiness probe to have something that can be used as a liveness probe.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
argo-workflows enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants