Tem•5mo ago

Kubernetes Readiness probe

@Max can you confirm this is correct config for readinessProbe?

httpGet:
    path: /api/public/health
    port: 3000
    scheme: HTTP
initialDelaySeconds: 15
timeoutSeconds: 5
periodSeconds: 5
successThreshold: 1
failureThreshold: 10

httpGet:
    path: /api/public/health
    port: 3000
    scheme: HTTP
initialDelaySeconds: 15
timeoutSeconds: 5
periodSeconds: 5
successThreshold: 1
failureThreshold: 10

10 Replies

Max•5mo ago

Please dont mention us directly. We try to come back to everyone in time while improving the product. The readiness probe looks good to me. Do you have any additional logs?

Max•5mo ago

If you run in kubernetes, also look at that: https://github.com/langfuse/langfuse-k8s/blob/main/charts/langfuse/templates/deployment.yaml#L93

GitHub

langfuse-k8s/charts/langfuse/templates/deployment.yaml at main · la...

Community-maintained Kubernetes config and Helm chart for Langfuse - langfuse/langfuse-k8s

Tem•5mo ago

sorry about that, try to exec to the container and receive this result

failed to create containerd task: failed to create shim task: OCI
            runtime create failed: runc create failed: unable to start container
            process: exec: "bash": executable file not found in $PATH: unknown

failed to create containerd task: failed to create shim task: OCI
            runtime create failed: runc create failed: unable to start container
            process: exec: "bash": executable file not found in $PATH: unknown

Max•5mo ago

what do the container logs look like?

Tem•5mo ago

theres no log, it failed at start

Max•5mo ago

Then try to give it more time to start up before you run the liveness probe

Tem•5mo ago

workfine if I remove liveness and readiness. Not sure why :<

Marc•5mo ago

if you check /api/public/health manually, does it work?

Tem•5mo ago

I found the issue, it because I did not set the HOSTNAME to 0.0.0.0 for Langfuse deploying on EKS

Marc•5mo ago

thanks!