You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the current implementation gives a false impression that multiple namespaces are supported (method called GetWatchNamespaces + plular used here). However, it's not the case. No matter what's in the WATCH_NAMESPACE env var, it just passes its content to the cache options when calling NewManager in operator's main.go.
Use-Case
more fine control over where Keda is looking for CRs. Now it's either 1 ns or all. Otherwise one has to install multiple KEDA w/ different namespaces in WATCH_NAMESPACE which leads to wasting of resources and configuration complexity (because some things are global, like the admission webhook)
Is this a feature you are interested in implementing yourself?
Yes
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Proposal
the current implementation gives a false impression that multiple namespaces are supported (method called
GetWatchNamespaces
+ plular used here). However, it's not the case. No matter what's in theWATCH_NAMESPACE
env var, it just passes its content to the cache options when callingNewManager
in operator'smain.go
.Use-Case
more fine control over where Keda is looking for CRs. Now it's either 1 ns or all. Otherwise one has to install multiple KEDA w/ different namespaces in
WATCH_NAMESPACE
which leads to wasting of resources and configuration complexity (because some things are global, like the admission webhook)Is this a feature you are interested in implementing yourself?
Yes
Anything else?
No response
The text was updated successfully, but these errors were encountered: