Red Hat OpenShift GitOps Operator, 1.19+, Notifications in Any Namespace

The "notifications in any namespace" feature is based on the "apps in any namespace" feature In the GitOps Operator, "apps in any namespace" can be configured by using a wildcard in the 'sourceNamespaces' list in the ArgoCD custom resource, but this does not work for "notifications in any namespace".

In a large, multi-tenant environment such as ours, we can only use this feature if wildcards can be used in the sourceNamespaces list.

For example, apps in any namespace is configured in the ArgoCD resource as:

spec:
  sourceNamespaces:
  - '*-tools'
  - '*-dev'
  - '*-test'
  - '*-prod' 

A similar setup for notifications is done as:

spec:
  notifications:
    enabled: true
    sourceNamespaces:
    - '*-tools'
    - '*-dev'
    - '*-test'
    - '*-prod'

Yet, this results in a failure to identify the matching namespaces for namespace-based notifications configuration.  The controller manager shows the following log messages:

skipping reconciliation of Notification resources for sourceNamespace *-tools as Apps in target sourceNamespace is not enabled
skipping reconciliation of Notification resources for sourceNamespace *-dev as Apps in target sourceNamespace is not enabled
skipping reconciliation of Notification resources for sourceNamespace *-test as Apps in target sourceNamespace is not enabled
skipping reconciliation of Notification resources for sourceNamespace *-prod as Apps in target sourceNamespace is not enabled 

Due to the nature of our large, dynamic, multi-tenant clusters, we cannot hard-code each individual namespace and are limited to the cluster level configuration for notifications, which does not meet the needs of part of our user base.

Please allow for the use of wildcards in the namespace list at /spec/notifications/sourceNamespaces.