Epic Goal

• RAG support in RHDH  Lightspeed
• This issue includes:
  • RAG support (from upstream) and any changes/extension that we need
  • Link RAG to RHDH documentation
    • Note: OpenShift Lightspeed shipped embeddings for their docs (for the last 2 versions of OpenShift) with the operator
    • We only have a small amount of RHDH documentation
    • Consider also including Backstage upstream documentation (stretch)
    • Should we add tech docs from plug ins that we’ve prebuilt?\ (moved to Stage 2)
  • backend API which act as a proxy for frontend to interact with the road-core RAG API (moved to Stage 2)

Why is this important?

• …

Scenarios

1. ...

Acceptance Criteria (Mandatory)

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

Open questions::

1. …

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