nats-queue-worker
nats-queue-worker copied to clipboard
openfaas
Queue-worker for OpenFaaS with NATS Streaming
## Expected Behaviour I have a function which runs ffmpeg to convert a video. It's CPU bound, so I've used HPAv2 to autoscale the pods running my function. This works...
In a previous conversion @alexellis and I discussed some items related to the queue worker, one of which being to verify whether or not the queue worker gracefully shuts down,...
In a previous conversion @alexellis and I discussed some items related to the queue worker, one of which being to verify whether or not the queue worker `ack_wait`s for multiple...
## Expected Behaviour Right now `faas-netes` exposes up a handy little CRD for `Function`s. At the moment, I find myself copying a live deployment of a `queue-worker` and turning that...
When asynchronous function execution completes the data is sent back to callback url. However if that callback URL issues 30x redirect (from http to https or similar), the data seems...
This issue is to gather research and opinions on how to tackle retries for certain HTTP codes. ## Expected Behaviour If a function returns certain errors like 429 (too busy)...
## Expected Behaviour Healthcheck over HTTP or an exec probe which can be used by Kubernetes to check readiness and health ## Current Behaviour N/a ## Possible Solution Please suggest...
## Expected Behaviour The subscriber (queue-worker) and publisher (gateway) should not try to reconnect if the connection is being broken due to SIGTERM/SIGINT. ## Current Behaviour Once #50 is merged...
## Feature: Non-repudiation for queue-worker callbacks Suggested by: Ed Wilde @ewilde We can use HMAC or RSA and HMAC together to sign messages when we use the X-Callback-Url. This means...
## Expected Behaviour The gateway and NATS queue worker both should reconnect if the connection is broken. ## Current Behaviour They do not reconnect. ## Possible Solution Solution being worked...