Epic Goal

What: enable Lightspeed to be fully aware of Argo CD context and allow users to query, inspect and troubleshoot Argo CD application deployments
Where: Lightspeed

Why is this important?

• ...

Scenarios

Reference documentation: https://docs.google.com/document/d/1_PZ7nx_AyFdGTlT7rw8tnjyGYTtKYk16kg8Yc46PEEQ/edit?usp=sharing

1. Deployment failure analysis
What: analyze and explain the reasons an Argo CD deployment has failed
Where: Console, Lightspeed
2. Metrics & health analysis
What: AI-analyzed health metrics summary based on Argo CD application healths metrics
Where: Console, Argo CD UI
3. Predictive deployment and risk analysis
What: analyze a range of signals (pipelines, security checks, policy checks, observability, etc) to predict the risk (e.g. risk score) associated with a new deployment
Where: ?

Other Considerations

• <Call out anything explicitly as Out of Scope?>
• <Call out internal and external dependencies?>
• <Are there any known previous works?>
• <Any unanswered questions?>

Definition of Ready

• The epic has been broken down into stories.
• Stories have been scoped.
• The epic has been stack ranked.

Definition of Done

• Code Complete:
  • All code has been written, reviewed, and approved.
• Tested:
  • Unit tests have been written and passed.
  • Integration tests have been completed.
  • System tests have been conducted, and all critical bugs have been fixed.
  • Tested on OpenShift either upstream or downstream on a local build.
• Documentation:
  • User documentation or release notes have been written.
• Build:
  • Code has been successfully built and integrated into the main repository / project.
• Review:
  • Code has been peer-reviewed and meets coding standards.
  • All acceptance criteria defined in the user story have been met.
  • Tested by reviewer on OpenShift.
• Deployment:
  • The feature has been deployed on OpenShift cluster for testing.
• Acceptance:
  • Product Manager or stakeholder has reviewed and accepted the work.