Uploaded image for project: 'OpenShift GitOps'
  1. OpenShift GitOps
  2. GITOPS-4045

Enable users to add/delete allowed source namespaces to/from AppProject via CLI

XMLWordPrintable

    • Enable users to add/delete allowed source namespaces to/from AppProject via CLI
    • False
    • None
    • False
    • To Do
    • SECFLOWOTL-97 - Promote Applications in Any Namespace to GA
    • 0% To Do, 0% In Progress, 100% Done
    • Hide
      With this update, two new commands are introduced for the 'Apps in Any Namespace' feature (#9755):

      argocd proj add-source-namespace: Enables users to add source namespaces to AppProject.Spec.SourceNamespaces, thereby whitelisting specific namespaces for application creation.
      argocd proj delete-source-namespace (also known as argocd proj remove-source-namespace): Allows users to remove source namespaces from AppProject.Spec.SourceNamespaces, thereby blacklisting specific namespaces.
      Show
      With this update, two new commands are introduced for the 'Apps in Any Namespace' feature (#9755): argocd proj add-source-namespace: Enables users to add source namespaces to AppProject.Spec.SourceNamespaces, thereby whitelisting specific namespaces for application creation. argocd proj delete-source-namespace (also known as argocd proj remove-source-namespace): Allows users to remove source namespaces from AppProject.Spec.SourceNamespaces, thereby blacklisting specific namespaces.
    • Enhancement
    • Done

      Epic Goal

      • add the below sub commands to ArgoCD CLI
        • argocd proj add-source-namespaces
        • argocd proj delete-source-namespaces

       

      Upstream ticket: https://github.com/argoproj/argo-cd/issues/16189

      Why is this important?

      • Users must be able to whitelist one or many namespaces for app creation via the CLI
      • Users must be able to blacklist one or many namespaces for app creation via the CLI

      Scenarios

      Adminstrative user of ArgoCD wants to whitelist/blacklist a tenant namespace to allow tenants to be able to create Argo Applications in their respective tenant namespaces. This has to be done via the AppProject by adding or removing the namespaces AppProject.Spec.SourceNamespaces. It would be preferable to do it via the CLI and the WebUI rather than users editing the source namespaces vi oc or kubectl client.

       

      Acceptance Criteria (Mandatory)

      • CI - MUST be running successfully with tests automated
      • Release Technical Enablement - Provide necessary release enablement details and documents.
      • CLI documentation is updated.

      Dependencies (internal and external)

      1. ...

      Previous Work (Optional):

      1. ...

      Open questions::

      1. ...
      •  

      Done Checklist

      • Acceptance criteria are met
      • Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
      • User Journey automation is delivered
      • Support and SRE teams are provided with enough skills to support the feature in production environment

              rshirur@redhat.com Raghavi Shirur (Inactive)
              rh-ee-anjoseph Anand Francis Joseph
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: