Feature Overview

This feature integrates OpenShift Lightspeed with OpenShift GitOps. It enables an AI-driven conversational interface within the OpenShift console to assist users with GitOps-related troubleshooting, resource management, and best practices.

Goals

• Contextual Assistance: Provide real-time answers to GitOps/Argo CD queries.

• Operational Intelligence: Analyze deployment failures, sync status, and metric health.

• Risk Assessment: Evaluate configurations against security and performance best practices.

• Actionable AI: Enable Lightspeed to execute commands (e.g., creating Application resources) via natural language.

Requirements

Use Cases

• New User - "How do I get started with Argo CD on OpenShift?" or "What is a Sync Policy?"
• Admin - "Audit my GitOps configuration for security risks" or "Optimize my resource hooks."
• Developer - "Why is my 'guestbook' application failing to sync?" or "Create a new Argo CD Application pointing to [Git Repo]."

Out of scope

• Model Training: We are utilizing existing LLMs/Foundational models, no custom model training.

Dependencies

Background, and strategic fit

Assumptions

< Are there assumptions being made regarding prerequisites and dependencies?>
< Are there assumptions about hardware, software or people resources?>

Customer Considerations

< Are there specific customer environments that need to be considered (such as working with existing h/w and software)?>

Documentation/QE Considerations

< 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? Possible values are: New Content, Updates to existing content, Release Note, or No Doc Impact?>
< Are there assumptions being made regarding prerequisites and dependencies?>
< Are there assumptions about hardware, software or people resources?>

Impact

< If the feature is ordered with other work, state the impact of this feature on the other work>

Related Architecture/Technical Documents

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).