-
Feature
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
False
-
-
False
-
-
0% To Do, 20% In Progress, 80% Done
-
-
The progressive sync feature was made available as alpha upstream in Argo CD 2.6 and OpenShift GitOps made it available as Tech Preview in v1.8.0 (https://issues.redhat.com/browse/GITOPS-956). This feature captures the work remaining to promote progressive sync to stable upstream and GA in the operator.
Goals
< Who benefits from this feature, and how? What is the difference between today’s current state and a world with this feature? >
Requirements
| Requirements | Notes | IS MVP |
| Upstream beta release | Targeting v1.16 | |
| Upstream stable release | Targeting v1.17 |
< What are we making, for who, and why/what problem are we solving?>
Out of scope
<Defines what is not included in this story>
Dependencies
< Link or at least explain any known dependencies. >
Background, and strategic fit
< What does the person writing code, testing, documenting need to know? >
Assumptions
< Are there assumptions being made regarding prerequisites and dependencies?>
< Are there assumptions about hardware, software or people resources?>
Customer Considerations
< Are there specific customer environments that need to be considered (such as working with existing h/w and software)?>
Documentation Considerations
< What educational or reference material (docs) is required to support this product feature? For users/admins? Other functions (security officers, etc)? >
What does success look like?
< Does this feature have doc impact? Possible values are: New Content, Updates to existing content, Release Note, or No Doc Impact?>
QE Contact
< Are there assumptions being made regarding prerequisites and dependencies?>
< Are there assumptions about hardware, software or people resources?>
Impact
< If the feature is ordered with other work, state the impact of this feature on the other work>
Related Architecture/Technical Documents
<links>
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
- is depended on by
-
ACM-17508 Validate and blog integration of standalone policy deployment with Argo Progressive Syncs
-
- Backlog
-
- relates to
-
GITOPS-6249 ApplicationSet Controller constantly reconciling with enable-progressive-syncs flag
-
- Closed
-
-
ACM-5653 RFE Policy support for progressive rollout strategies
-
- New
-
-
ACM-15025 ACM Make progressive sync stable/work with RHACM Gitops
-
- New
-