Support using a custom NATS Streaming channel and queue group. #1399
Description
My actions before raising this issue
- Followed the troubleshooting guide
- Read/searched the docs
- Searched past issues
Expected Behaviour
OpenFaaS should allow for customising the NATS Streaming channel and queue group used for asynchronous invocations instead of using the hardcoded faas-request channel and faas queue group. This would allow, for example, to have different deployments of OpenFaaS (in the same or in separate Kubernetes clusters) being serviced by the same NATS Streaming cluster.
Current Behaviour
OpenFaaS and the NATS queue worker use the hardcoded faas-request channel and faas queue group.
Possible Solution
Allow for overriding the name of the channel via a faas_nats_topic environment variable.
Steps to Reproduce (for bugs)
- N/A
- N/A
- N/A
- N/A
Context
We will be using a single NATS Streaming cluster to service three different OpenFaaS deployments (across three different Kubernetes clusters), and we need to make sure that invocations of functions in cluster K1 do not end up being processed by queue workers in cluster K2 or K3.
Your Environment
- FaaS-CLI version ( Full output from:
faas-cli version):
N/A
- Docker version
docker version(e.g. Docker 17.0.05 ):
N/A
- Are you using Docker Swarm or Kubernetes (FaaS-netes)?
Kubernetes
- Operating System and version (e.g. Linux, Windows, MacOS):
N/A
- Code example or link to GitHub repo or gist to reproduce problem:
N/A
- Other diagnostic information / logs from troubleshooting guide
N/A
Next steps
You may join Slack for community support.