How can I implement KEDA for multiple namespaces

[harshik9]

Currently i have 4 namespaces on my cluster and each namespace belongs to a project. I was successful in implementing KEDA for one namespace. The problem is when I try to Implement the kind:APIService for another namespace, the one that I have already implemented gets replaced with the new one. How can i make this work for different namespaces.

Keda1-namespace.txt
Keda2-namespace.txt

we are scaling applications based on the confluent kafka partition

[zroubalik]

Unfortunately it is not possible to install mutliple KEDA instances on one cluster, this needs to be solved first #470 (TLDR Metrics Adapter doesn't allow this, as you correctly mentioned that the APIService object gets replaced, as there could be only one such resource in the cluster).

But you can setup your KEDA to watch all namespaces (that's the default setting), thus scaling will be working across all of them.

[sidharthkumarpradhan]

Hello @JorTurFer, I hope you had a great weekend. I wanted to let you know, that I have deployed two keda-operator in the keda namespace, specifying the different namespace in them. The problem right now is, at a given time only one of them is getting activated and the other one is in a waiting state. I checked the logs, and here is what I see. It is stuck in the leader selection stage only.

Appreciate your help on this. Thanks

[sidharthkumarpradhan]

Hello @JorTurFer, I hope you are doing great. It seems like we have been stuck with this namespace issue. I even tried to deploy multiple metrics servers and admission webhook as I see they also have WATCH_NAMESPACE env field. Not that is also not working for all the namespaces, only one namespace is working. Any thoughts on this or anything else we are missing. I will be thankful for any help on this.

[JorTurFer]

Multiple metrics servers won't work at all because they use a unique resource (external.metrics.k8s.io), nothing can be done there. About multiple webhooks, they could work but probably you need to tune the admission webhook configuration (the manifest) to filter what is processed by whom.
About the leader election, you can disable it removing the argument: --leader-elect but in that case, you must ensure that you don't have 2 keda operator instances watching the same namespace or they will be in conflict between them

[sidharthkumarpradhan]

Thank you so much @JorTurFer for responding. I have also tried to deploy all these in a particular namespace with Requisite permission. I even tried --leader-elect=false. I am attaching my final deployment file that I tried in a separate namespace below. Nothing is working. Thanks, Man!. Really appreciate your time.

https://gist.github.com/sidharthkumarpradhan/e457d5cd586af3fd1d03fc10645a9b4b

[JorTurFer]

Nice to know that you have it working, it's a bit tricky, but currently we don't have any other option for it. As I said, we are working on it, but for the moment...

[sidharthkumarpradhan]

One update, we have tried to use the the array way to specify the namespaces. Even it is not working.

Any help on this @zroubalik @tomkerkhove @JorTurFer
Appreciated. Thanks