Right now faas-netes exposes up a handy little CRD for Functions.
At the moment, I find myself copying a live deployment of a queue-worker and turning that into a helm template, which is slightly dangerous because it means that users using more than the default queue are likely all bespoke to a certain degree.
It would be nice to be able to define a Queue as a CRD similar to a Function, which would allow things like the Pro queue worker and standard queue worker to be bundled under one resource type.
That, and it would be nice to see the things like queue capacity in k9s by simply typing :queue, but that's another story.
Current Behaviour
There is not a CRD for this right now.
Possible Solution
Steps to Reproduce (for bugs)
Context
Not DIY my own queue worker deployments, which can potentially cause drift from OF and may increase the need for troubleshooting if a DIY deployment is using a version with different behavior than the default queue worker.
Also, it makes it possible (perhaps likely) to have different functions using different queue workers that all have different images, because image tag wasn't exposed in a template or the like.
Your Environment
FaaS-CLI version ( Full output from: faas-cli version ):
0.13.13
Docker version docker version (e.g. Docker 17.0.05 ):
20.10.8
What version and distriubtion of Kubernetes are you using? kubectl version
server v1.21.3
client v1.22.2
Operating System and version (e.g. Linux, Windows, MacOS):
MacOS
Link to your project or a code example to reproduce issue:
What network driver are you using and what CIDR? i.e. Weave net / Flannel
Expected Behaviour
Right now
faas-netesexposes up a handy little CRD forFunctions.At the moment, I find myself copying a live deployment of a
queue-workerand turning that into a helm template, which is slightly dangerous because it means that users using more than the default queue are likely all bespoke to a certain degree.It would be nice to be able to define a
Queueas a CRD similar to aFunction, which would allow things like the Pro queue worker and standard queue worker to be bundled under one resource type.That, and it would be nice to see the things like queue capacity in
k9sby simply typing:queue, but that's another story.Current Behaviour
There is not a CRD for this right now.
Possible Solution
Steps to Reproduce (for bugs)
Context
Not DIY my own queue worker deployments, which can potentially cause drift from OF and may increase the need for troubleshooting if a DIY deployment is using a version with different behavior than the default queue worker.
Also, it makes it possible (perhaps likely) to have different functions using different queue workers that all have different images, because image tag wasn't exposed in a template or the like.
Your Environment
FaaS-CLI version ( Full output from:
faas-cli version): 0.13.13Docker version
docker version(e.g. Docker 17.0.05 ): 20.10.8What version and distriubtion of Kubernetes are you using?
kubectl versionserver v1.21.3 client v1.22.2Operating System and version (e.g. Linux, Windows, MacOS): MacOS
Link to your project or a code example to reproduce issue:
What network driver are you using and what CIDR? i.e. Weave net / Flannel