Feature Description
To effectively use kubernetes and flowise in queue mode, we want to be able to know if a flowise worker pod is up or down, so that when we are rolling out new versions, we only remove the healthy old pods if the ones become healthy too.
Flowise-Main offers this, on the /api/v1/ping endpoint but Flowise-Worker does not:
=== flowise-worker ===
$ kubectl exec -n flowise \
$(kubectl get pod -n flowise -l app.kubernetes.io/name=flowise-worker -o jsonpath='{.items[0].metadata.name}') \
-- curl -sv http://localhost:3000/api/v1/ping
* Host localhost:3000 was resolved.
* IPv6: ::1
* IPv4: 127.0.0.1
* Trying [::1]:3000...
* connect to ::1 port 3000 from ::1 port 46606 failed: Connection refused
* Trying 127.0.0.1:3000...
* connect to 127.0.0.1 port 3000 from 127.0.0.1 port 46108 failed: Connection refused
* Failed to connect to localhost port 3000 after 0 ms: Could not connect to server
* closing connection #0
command terminated with exit code 7
=== flowise-main ===
$ kubectl exec -n flowise \
$(kubectl get pod -n flowise -l app.kubernetes.io/name=flowise-main -o jsonpath='{.items[0].metadata.name}') \
-- curl -sv http://localhost:3000/api/v1/ping
* Host localhost:3000 was resolved.
* IPv6: ::1
* IPv4: 127.0.0.1
* Trying [::1]:3000...
* Connected to localhost (::1) port 3000
* using HTTP/1.x
> GET /api/v1/ping HTTP/1.1
> Host: localhost:3000
> User-Agent: curl/8.14.1
> Accept: */*
>
* Request completely sent off
< HTTP/1.1 200 OK
< Vary: Origin
< Access-Control-Allow-Credentials: true
< Content-Type: text/html; charset=utf-8
< Content-Length: 4
< ETag: W/"4-DlFKBmK8tp3IY5U9HOJuPUDoGoc"
< Date: Thu, 09 Apr 2026 04:18:02 GMT
< Connection: keep-alive
< Keep-Alive: timeout=5
<
{ [4 bytes data]
* Connection #0 to host localhost left intact
pong%
Feature Category
Performance
Problem Statement
Improves kubernetes live cycle and ensuring healthy pods exist
Proposed Solution
Adding a health check endpoint to workers that returns 200 if the app is healthy
Mockups or References
No response
Additional Context
No response
Feature Description
To effectively use kubernetes and flowise in queue mode, we want to be able to know if a flowise worker pod is up or down, so that when we are rolling out new versions, we only remove the healthy old pods if the ones become healthy too.
Flowise-Main offers this, on the /api/v1/ping endpoint but Flowise-Worker does not:
Feature Category
Performance
Problem Statement
Improves kubernetes live cycle and ensuring healthy pods exist
Proposed Solution
Adding a health check endpoint to workers that returns 200 if the app is healthy
Mockups or References
No response
Additional Context
No response