I see in the csv that we're declaring support for two installModes:

installModes:
    - supported: true
      type: OwnNamespace
    - supported: true
      type: SingleNamespace
    - supported: false
      type: MultiNamespace
    - supported: false
      type: AllNamespaces

From the other issue #12545 (comment) the user is then responsible for setting env variables:

QUARKUS_OPERATOR_SDK_CONTROLLERS_KEYCLOAKCONTROLLER_NAMESPACES
QUARKUS_OPERATOR_SDK_CONTROLLERS_KEYCLOAKREALMIMPORTCONTROLLER_NAMESPACES

I can confirm that when you use all namespaces, you do see the primary informers start watching everything:

Starting informer for namespace: JOSDK_ALL_NAMESPACES resource: Keycloak

However this setting does not influence the informers registered by prepareEventSources, the namespace it obtains from the client configuration is the current namespace, so we'll only watch dependent resources in the current namespace.

To confirm, the expectation here is to support all InstallModes (defaulting to current namespace) and let the user set env variables as necessary for anything else.

Uh oh!

Descoped mode for the Operator #15888

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions