Skip to content

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

Description

@fouadsemaan

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

  1. Set your watch namespace to any tenant besides the release namespace.
  2. Create a scaled object in the release namespace.
  3. 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

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions