Major Feature Overview
Improve the user experience of working with Argo CD, Argo Rollouts and workloads that are managed through GitOps within the OpenShift Console.
Goals
- Increase the value of using Argo CD with OpenShift
- Reduce context switch between OpenShift Console and Argo CD dashboard in common user flows
Requirements
| Requirements | Notes | IS MVP |
| Argo CD and Argo Rollouts resources are accessible through Console navigation | Y | |
| Rollouts resources are visible and enriched to the same level as Deployments in Topology | Y | |
| Visual cues available in Console for resources that are managed by Argo CD | Y | |
| Provide a rapid path for importing a GitOps git repository to Argo CD through console | Y |
Use Cases
- Enable access to Argo CD and Argo Rollouts resources and configurations through Console navigation
- Enable visibility for Rollouts at the same level as Deployments
- Provide visual cues for GitOps-enabled workloads and resurrect in Console to avoid accidental edit through console
- Reduce the steps for onboarding a GitOps git repository to Argo CD
Out of scope
TBD
Dependencies
Console dynamic plugin framework
Background, and strategic fit
TBD
Assumptions
TBD
Customer Considerations
TBD
Documentation/QE Considerations
TBD
Impact
TBD
Related Architecture/Technical Documents
TBD
Definition of Ready
- The objectives of the feature are clearly defined and aligned with the business strategy.
- All feature requirements have been clearly defined by Product Owners.
- The feature has been broken down into epics.
- The feature has been stack ranked.
- Definition of the business outcome is in the Outcome Jira (which must have a parent Jira).
- …
- duplicates
-
GITOPS-4600 Progressive Delivery in OpenShift Console's Topology View
-
- Closed
-
- is related to
-
RFE-6455 Identify Resources Managed by Argo CD in OpenShift Console
-
- Backlog
-