Epic Goal

Enable Lightspeed to provide Argo CD–aware, query-driven assistance, helping users understand, reason about, and troubleshoot GitOps workflows on OpenShift.

Why is this important?

Currently, when Lightspeed is configured on OpenShift, GitOps-related queries often result in generic or low-context responses that do not align with Argo CD concepts or operational workflows.

Lightspeed lacks sufficient Argo CD domain awareness to deliver accurate, actionable guidance.

Example: Lightspeed give inaccurate information when asked about image pull polices for gitops components

As Lightspeeds adoption increases for platform guidance, without Argo CD context awareness:

• GitOps-related responses lack precision

• Users may receive misleading or overly generic explanations

• Troubleshooting workflows become less effective

• Overall user trust and productivity are impacted

Lightspeed should function as a reliable knowledge and reasoning assistant for GitOps concepts.

Scenarios

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

Conceptual / Learning Queries

Examples:

• “How do I get started with Argo CD on OpenShift?”
• “What is a Sync Policy?”
• “What does OutOfSync mean?”
• “What is the difference between automated and manual sync?”

Expected Behavior:{}

Lightspeed provides structured, Argo CD–aware explanations aligned with OpenShift GitOps workflows.

Operational / Reasoning Queries{}

Examples:

• “Why would an application become OutOfSync?”
• “What causes a Degraded health status?”
• “Why is my sync taking too long?”

Expected Behavior:
Lightspeed offers plausible causes, reasoning paths, and troubleshooting guidance.

Troubleshooting with User-Provided Context{}

Examples:

• User pastes sync error logs
• User provides controller/repo-server errors
• User shares failure messages

Expected Behavior:
Lightspeed interprets supplied information and provides targeted guidance.

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.