Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-7191

Support for  wildcards (*)  in the `.spec.applicationSet.sourceNamespaces` field

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • GitOps
    • None
    • False
    • None
    • False
    • Not Selected

      1. Proposed title of this feature request

      Support for  wildcards (*)  in the `.spec.applicationSet.sourceNamespaces` field.

      2. What is the nature and description of the request?

      For the OpenShift GitOps Operator we would like the AppSets in any namespace feature to support wildcards in the sourceNamespace list. The current operator version does not support wildcards in the configuration and requires us to maintain an explicit list of namespaces.

      https://docs.openshift.com/gitops/1.15/argocd_application_sets/managing-app-sets-in-non-control-plane-namespaces.html#gitops-enabling-the-application-set-resources-in-non-control-plane-namespaces_managing-app-sets-in-non-control-plane-namespaces

      3. Why does the customer need this? (List the business requirements here)

      Currently, they cannot use the AppSets in any namespace feature because of the lack of wildcard support for the source namespace list andt hey want to automatically add new projects when they are created.

      4. List any affected packages or components.

      ApplicationSet

              halawren@redhat.com Harriet Lawrence
              rhn-support-disharma Diksha Sharma
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: