Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multiple namespaces passed to WATCH_NAMESPACE #5670

Closed
jkremser opened this issue Apr 9, 2024 · 0 comments · Fixed by #5631 or kedacore/keda-docs#1357
Closed

Multiple namespaces passed to WATCH_NAMESPACE #5670

jkremser opened this issue Apr 9, 2024 · 0 comments · Fixed by #5631 or kedacore/keda-docs#1357
Labels
feature-request All issues for new features that have not been committed to needs-discussion

Comments

@jkremser
Copy link
Contributor

jkremser commented Apr 9, 2024

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 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

@jkremser jkremser added feature-request All issues for new features that have not been committed to needs-discussion labels Apr 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request All issues for new features that have not been committed to needs-discussion
Projects
Status: Ready To Ship
1 participant