Add OpenFaaS Pro queue-worker to faas-netes helm chart #851
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Signed-off-by: Alex Ellis (OpenFaaS Ltd) alexellis2@gmail.com
Description
Add OpenFaaS Pro queue-worker to faas-netes helm chart
This PR enables retries and backoff for Pro customers through an enhanced queue-worker.
See, the per-queue-worker configuration:
To enable it, set
queueWorkerPro.enabled=true
with helm or arkadeMotivation and Context
The OpenFaaS Pro queue-worker is a new feature for paying customers
How Has This Been Tested?
Running
kubectl logs -n openfaas deploy/queue-worker
showed the new worker taking over when installed with helm, then I was able to run an async invocation against nodeinfo and see its response executing. I also confirmed that the existing queue-worker carried on workign when the pro version was disabled.Types of changes
Checklist: