-
Feature
-
Resolution: Unresolved
-
Major
-
None
-
False
-
-
False
-
Not Selected
Feature Overview
...
Goals
Provide a seamless, transparent user experience for configuring and observing GitOps Pull models (Basic and Advanced/Agent) through the OpenShift/RHACM UI, utilizing the existing GitOps Addon for unified lifecycle management, while initiating a strategic evaluation to consolidate into a single Advanced (Agent) model long-term.
User Context Currently, customers managing multi-cluster environments via OpenShift GitOps and RHACM have access to two distinct pull-based deployment architectures:
relevant links
https://github.com/stolostron/multicloud-integrations/blob/main/gitopsaddon/README.md
Basic Pull Model: Wraps Argo CD Applications in OCM ManifestWork objects and relies on the skip-reconcile annotation. It only provides basic sync and health status feedback to the Hub.
Advanced Pull Model (Argo CD Agent): Powered by the argocd-agent, delivering superior UI integration with full application status synchronization, detailed resource health, and live state comparison directly in the Argo CD UI.
Because both models exist, users experience UI discrepancies (e.g., the Basic model lacks resource trees and live states, which might look like a UI failure) and deployment fragmentation. The OCM GitOpsCluster custom resource and GitOps Addon framework already possess the capability to automate the setup for both, but the UI needs to accurately reflect these differing capabilities, and a long-term architectural decision is required to reduce maintenance overhead.
Expected User Outcome(s)
• Accurate UI Rendering: For Advanced (Agent) clusters, users see the full Argo CD experience (resource tree, live state, detailed sync errors). For Basic clusters, the UI gracefully handles the limited status data without displaying broken panes or missing data errors.
• Simplified Future Roadmap: Users have a clear understanding of the platform's architectural direction, preparing them for the eventual deprecation of the Basic Pull Model in favor of the fully integrated Argo CD Agent.
Requirements
This Section: A list of specific needs or objectives that a Feature must
deliver to satisfy the Feature.. Some requirements will be flagged as MVP.
If an MVP gets shifted, the feature shifts. If a non MVP requirement slips,
it does not shift the feature.
| Requirement | Notes | isMvp? |
|---|---|---|
| CI - MUST be running successfully with test automation | This is a requirement for ALL features. |
YES |
| Release Technical Enablement | Provide necessary release enablement details and documents. |
YES |
(Optional) Use Cases
This Section:
- Main success scenarios - high-level user stories
- Alternate flow/scenarios - high-level user stories
- ...
Questions to answer
- ...
Out of Scope
- …
Background, and strategic fit
This Section: What does the person writing code, testing, documenting
need to know? What context can be provided to frame this feature?
Assumptions
- ...
Customer Considerations
- ...
Documentation Considerations
Questions to be addressed:
- What educational or reference material (docs) is required to support this
product feature? For users/admins? Other functions (security officers, etc)? - Does this feature have a doc impact?
- New Content, Updates to existing content, Release Note, or No Doc Impact
- If unsure and no Technical Writer is available, please contact Content
Strategy. - What concepts do customers need to understand to be successful in
[action]? - How do we expect customers will use the feature? For what purpose(s)?
- What reference material might a customer want/need to complete [action]?
- Is there source material that can be used as reference for the Technical
Writer in writing the content? If yes, please link if available. - What is the doc impact (New Content, Updates to existing content, or
Release Note)?
- relates to
-
-
- New
-
