Skip to content

Conversation

syedriko
Copy link
Contributor

@syedriko syedriko commented Oct 9, 2025

Description

Added a new field to the OLS RAG configuration - product_docs_origin -

ols_config:
  reference_content:
    indexes:
      product_docs_origin

that the OLS will use to identify the source of the RAG database. For BYOK RAG sources, product_docs_origin is set to the BYOK image name:tag. For OCP docs, it is set to "Red Hat OpenShift x.y documentation"
The corresponding service PR is openshift/lightspeed-service#2630

Type of change

  • Refactor
  • New feature
  • Bug fix
  • CVE fix
  • Optimization
  • Documentation Update
  • Configuration Update
  • Bump-up dependent library

Related Tickets & Documents

Checklist before requesting a review

  • I have performed a self-review of my code.
  • PR has passed all pre-merge test jobs.
  • If it is a core feature, I have added thorough tests.

Testing

  • Please provide detailed steps to perform tests related to this code change.
  • How were the fix/results from this change verified? Please provide relevant screenshots or results.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Oct 9, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 9, 2025

@syedriko: This pull request references OLS-2166 which is a valid jira issue.

In response to this:

Description

Added a new field to the OLS RAG configuration - product_docs_origin -
ols_config:
reference_content:
indexes:
product_docs_origin

that the OLS will use to identify the source of the RAG database. For BYOK RAG sources product_docs_origin is set to the BYOK image name:tag. For OCP docs, it is set to "Red Hat OpenShift x.y documentation"

Type of change

  • Refactor
  • New feature
  • Bug fix
  • CVE fix
  • Optimization
  • Documentation Update
  • Configuration Update
  • Bump-up dependent library

Related Tickets & Documents

  • Related Issue #
  • Closes #

Checklist before requesting a review

  • I have performed a self-review of my code.
  • PR has passed all pre-merge test jobs.
  • If it is a core feature, I have added thorough tests.

Testing

  • Please provide detailed steps to perform tests related to this code change.
  • How were the fix/results from this change verified? Please provide relevant screenshots or results.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot requested review from bparees and raptorsun October 9, 2025 04:11
@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 9, 2025

@syedriko: This pull request references OLS-2166 which is a valid jira issue.

In response to this:

Description

Added a new field to the OLS RAG configuration - product_docs_origin -
ols_config:
reference_content:
indexes:
product_docs_origin

that the OLS will use to identify the source of the RAG database. For BYOK RAG sources product_docs_origin is set to the BYOK image name:tag. For OCP docs, it is set to "Red Hat OpenShift x.y documentation"

Type of change

  • Refactor
  • New feature
  • Bug fix
  • CVE fix
  • Optimization
  • Documentation Update
  • Configuration Update
  • Bump-up dependent library

Related Tickets & Documents

Checklist before requesting a review

  • I have performed a self-review of my code.
  • PR has passed all pre-merge test jobs.
  • If it is a core feature, I have added thorough tests.

Testing

  • Please provide detailed steps to perform tests related to this code change.
  • How were the fix/results from this change verified? Please provide relevant screenshots or results.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 9, 2025

@syedriko: This pull request references OLS-2166 which is a valid jira issue.

In response to this:

Description

Added a new field to the OLS RAG configuration - product_docs_origin -
ols_config:
reference_content:
indexes:
product_docs_origin

that the OLS will use to identify the source of the RAG database. For BYOK RAG sources, product_docs_origin is set to the BYOK image name:tag. For OCP docs, it is set to "Red Hat OpenShift x.y documentation"

Type of change

  • Refactor
  • New feature
  • Bug fix
  • CVE fix
  • Optimization
  • Documentation Update
  • Configuration Update
  • Bump-up dependent library

Related Tickets & Documents

Checklist before requesting a review

  • I have performed a self-review of my code.
  • PR has passed all pre-merge test jobs.
  • If it is a core feature, I have added thorough tests.

Testing

  • Please provide detailed steps to perform tests related to this code change.
  • How were the fix/results from this change verified? Please provide relevant screenshots or results.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@syedriko syedriko marked this pull request as draft October 9, 2025 04:15
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Oct 9, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 9, 2025

@syedriko: This pull request references OLS-2166 which is a valid jira issue.

In response to this:

Description

Added a new field to the OLS RAG configuration - product_docs_origin -

ols_config:
 reference_content:
   indexes:
     product_docs_origin

that the OLS will use to identify the source of the RAG database. For BYOK RAG sources, product_docs_origin is set to the BYOK image name:tag. For OCP docs, it is set to "Red Hat OpenShift x.y documentation"

Type of change

  • Refactor
  • New feature
  • Bug fix
  • CVE fix
  • Optimization
  • Documentation Update
  • Configuration Update
  • Bump-up dependent library

Related Tickets & Documents

Checklist before requesting a review

  • I have performed a self-review of my code.
  • PR has passed all pre-merge test jobs.
  • If it is a core feature, I have added thorough tests.

Testing

  • Please provide detailed steps to perform tests related to this code change.
  • How were the fix/results from this change verified? Please provide relevant screenshots or results.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 9, 2025

@syedriko: This pull request references OLS-2166 which is a valid jira issue.

In response to this:

Description

Added a new field to the OLS RAG configuration - product_docs_origin -

ols_config:
 reference_content:
   indexes:
     product_docs_origin

that the OLS will use to identify the source of the RAG database. For BYOK RAG sources, product_docs_origin is set to the BYOK image name:tag. For OCP docs, it is set to "Red Hat OpenShift x.y documentation"
The corresponding service PR is openshift/lightspeed-service#2630

Type of change

  • Refactor
  • New feature
  • Bug fix
  • CVE fix
  • Optimization
  • Documentation Update
  • Configuration Update
  • Bump-up dependent library

Related Tickets & Documents

Checklist before requesting a review

  • I have performed a self-review of my code.
  • PR has passed all pre-merge test jobs.
  • If it is a core feature, I have added thorough tests.

Testing

  • Please provide detailed steps to perform tests related to this code change.
  • How were the fix/results from this change verified? Please provide relevant screenshots or results.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@syedriko
Copy link
Contributor Author

syedriko commented Oct 9, 2025

/retest

@syedriko syedriko marked this pull request as ready for review October 9, 2025 19:11
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Oct 9, 2025
@syedriko
Copy link
Contributor Author

syedriko commented Oct 9, 2025

/retest

@openshift-ci openshift-ci bot requested a review from joshuawilson October 9, 2025 19:12
@syedriko
Copy link
Contributor Author

/retest

referenceIndex := ReferenceIndex{
ProductDocsIndexPath: filepath.Join(RAGVolumeMountPath, fmt.Sprintf("rag-%d", i)),
ProductDocsIndexId: index.IndexID,
ProductDocsOrigin: index.Image,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@syedriko What will be the indexOrigin name for BYOK images ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For a BYOK image, its ProductDocsOrigin will be its image:tag. For example,

ols:
    rag:
    - image: quay.io/openshift-lightspeed-test/assisted-installer-guide:2025-1

will log

[ols.src.rag_index.index_loader:index_loader.py:148] INFO: Loading vector index #0 from quay.io/openshift-lightspeed-test/assisted-installer-guide:2025-1...
...
[ols.src.rag_index.index_loader:index_loader.py:148] INFO: Loading vector index #1 from Red Hat OpenShift 4.19 documentation...

@raptorsun
Copy link
Contributor

/lgtm
/approve

/test bundle-e2e-4-19

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 13, 2025
Copy link

openshift-ci bot commented Oct 13, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: raptorsun

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 13, 2025
Copy link

openshift-ci bot commented Oct 13, 2025

@syedriko: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@syedriko
Copy link
Contributor Author

/retest

@openshift-merge-bot openshift-merge-bot bot merged commit 3dbe16c into openshift:main Oct 13, 2025
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants