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

Applications sync order

    XMLWordPrintable

Details

    • Applications sync order
    • False
    • False
    • To Do
    • 100
    • 100% 100%
    • Hide
      This is a Alpha Feature.

      Adds support for ApplicationSet Progressive Rollout Strategy. Using this feature a user can enhance the ArgoCD ApplicationSet resource to embed a rollout strategy for a progressive application resource update after the ApplicationSet spec or Application templates are modified.

      When this enhancement is enabled, Applications are updated in a declarative order, instead of simultaneously.
      Show
      This is a Alpha Feature. Adds support for ApplicationSet Progressive Rollout Strategy. Using this feature a user can enhance the ArgoCD ApplicationSet resource to embed a rollout strategy for a progressive application resource update after the ApplicationSet spec or Application templates are modified. When this enhancement is enabled, Applications are updated in a declarative order, instead of simultaneously.

    Description

      Goal

      As an admin, I want to control the sync order of applications relative to each other and number of simultaneous syncs in progress so that I can manage dependencies between applications and sync certain apps before others when a change triggers both to sync, without triggering mass syncs across the Argo CD instance.

      The following upstream RFE refers to this capabilities specifically for ApplicationSets, to match a similar capabitiy that users could do via app of apps pattern:
      https://github.com/argoproj-labs/applicationset/issues/221

      Acceptance Criteria

      • User can specify the order of application syncs relative to each other similar to sync waves

      Attachments

        Issue Links

          is related to

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. GITOPS-885 R&D Application hooks

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              aveerama@redhat.com Abhishek Veeramalla
              rh-ee-chernand Christian Hernandez (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: