charts
charts copied to clipboard
Release namespace (Keda) is now automatically added to list of namespaces for which to create role bindings if watch namespace is set but is NOT added to watch namespace ENV VAR
When watchNamespace value is set, the release namespace (keda by default) automatically gets added to list of namespaces to have the appropriate rolebindings but it is not added to the WATCH_NAMESPACE env var.
Expected Behavior
When setting watchNamespace, the releaseNamespace is automatically included to have the rolebinding AND it should include releaseNamespace in the WATCH_NAMESPACE ENV Var in the manager deployment.
Actual Behavior
The release namespace is NOT included in the WATCH_NAMESPACE env variable when setting the watch namespace.
Steps to Reproduce the Problem
- Set your watch namespace to any tenant besides the release namespace.
- Create a scaled object in the release namespace.
- It will not be picked up since the release namespace is NOT watched.
Specifications
- **KEDA Version: 2.17.0
- **Platform & Version:
- **Kubernetes Version: 1.30.7
- **Scaler(s): N/A