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

Application isolation when setting spec.sourceNamespace to '*' using Applications in any any Namespace feature

XMLWordPrintable

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

      1. Proposed title of this feature request

      Application isolation when setting spec.sourceNamespace to '*' using Applications in any any Namespace

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

      Customer wants to isolate particular namespaces which otherwise match the wildcard pattern in `spec.sourceNamespaces` when using Applications in any namespace feature.

      Also, customer wants to restrict one cluster scoped instance of ArgoCD from deploying applications already deployed by another cluster scoped instance of ArgoCD when deployed on the same cluster. This should allow any cluster scoped ArgoCD instance to use the "*" for sourceNamespaces as applications deployed on the same cluster by any other cluster scoped ArgoCD instance should be ignored.

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

      • When deploying Applications in Any namespace and while using the "*" value for sourceNamespaces, we've noticed undesired behavior in the way applications are deployed. When there are multiple ArgoCD instances on the cluster (deployed in different namespaces), one instance of ArgoCD deploys the same applications already deployed by another instance. This is undesirable.
      •  Since our cluster scoped ArgoCD instances will be used for different types of applications, we will need to keep those applications seperate.

       

      4. List any affected packages or components.

            halawren@redhat.com Harriet Lawrence
            rhn-support-jyarora Jyotsana Arora
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: