Epic Goal
Breaking the original epic (https://issues.redhat.com/browse/GITOPS-3050) into smaller manageable epics. This specifically is for Argo CD Applications
Why is this important?
- Eliminates the need for users to bounce between different user interfaces providing a consistent experience
- Further differentiates OpenShift GitOps from Argo CD
Scenarios
- Managing OpenShift GitOps custom resources from the OpenShift console
Acceptance Criteria (Mandatory)
- CI - MUST be running successfully with tests automated
- Release Technical Enablement - Provide necessary release enablement details and documents.
- Argo CD applications are accessible through the navigation in the Console
Dependencies (internal and external)
- OpenShift Dynamic Console SDK
Previous Work (Optional):
https://github.com/gnunn-gitops/gitops-admin-plugin
Open questions::
- Resource based Console UI versus ACM versus Backstage versus existing Environments tab
- Pure resource based or hybrid resource/API based model. Currently POC is pure resource based however work was done on Hybrid which revealed a number of challenges.
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
- clones
-
GITOPS-3050 Argo Rollouts in Console
-
- To Do
-