Skip to content

OLS-1953: Create OLS 1.0.3 release notes #96545

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: lightspeed-docs-main
Choose a base branch
from

Conversation

rh-tokeefe
Copy link
Contributor

@rh-tokeefe rh-tokeefe commented Jul 23, 2025

Affects:
lightspeed-main
lightspeed-docs-1.0

PR must be CP'd back to the lightspeed-docs-1.0 branch.

Version(s): 1.0

Issue: https://issues.redhat.com/browse/OLS-1953

Link to docs preview:
https://96545--ocpdocs-pr.netlify.app/openshift-lightspeed/latest/release_notes/ols-release-notes.html#ols-1-0-3-release-notes_ols-release-notes

QE review:

  • QE has approved this change.

Additional information:

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

openshift-ci-robot commented Jul 23, 2025

@rh-tokeefe: This pull request references OLS-1953 which is a valid jira issue.

In response to this:

Version(s):

Issue:

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:

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 added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Jul 23, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jul 23, 2025

@rh-tokeefe: This pull request references OLS-1953 which is a valid jira issue.

In response to this:

Affects:
lightspeed-main
lightspeed-docs-1.0

PR must be CP'd back to the lightspeed-docs-1.0 branch.

Version(s): 1.0

Version(s): 1.0

Issue: https://issues.redhat.com/browse/OLS-1953

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:

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 Jul 23, 2025

@rh-tokeefe: This pull request references OLS-1953 which is a valid jira issue.

In response to this:

Affects:
lightspeed-main
lightspeed-docs-1.0

PR must be CP'd back to the lightspeed-docs-1.0 branch.

Version(s): 1.0

Issue: https://issues.redhat.com/browse/OLS-1953

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:

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.

@ocpdocs-previewbot
Copy link

ocpdocs-previewbot commented Jul 23, 2025

🤖 Tue Jul 29 14:24:18 - Prow CI generated the docs preview:

https://96545--ocpdocs-pr.netlify.app/openshift-lightspeed/latest/release_notes/ols-release-notes.html

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jul 23, 2025

@rh-tokeefe: This pull request references OLS-1953 which is a valid jira issue.

In response to this:

Affects:
lightspeed-main
lightspeed-docs-1.0

PR must be CP'd back to the lightspeed-docs-1.0 branch.

Version(s): 1.0

Issue: https://issues.redhat.com/browse/OLS-1953

Link to docs preview:
https://96545--ocpdocs-pr.netlify.app/openshift-lightspeed/latest/release_notes/ols-release-notes.html#ols-1-0-3-release-notes_ols-release-notes

QE review:

  • QE has approved this change.

Additional information:

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 added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Jul 25, 2025
indexID: vector_db_index
----
+
Previously, you had to manually define the parameter values.
Copy link
Contributor

@syedriko syedriko Jul 29, 2025

Choose a reason for hiding this comment

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

This emphasizes the wrong side of the equation. The key to this change is that from now on it is only necessary to specify the BYOK image and not these two parameters. Users don't need know they exist and what values they hold. All they need to know is the name of the BYOK image.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thanks for the comment @syedriko. I pushed a change.

I know you mentioned the customer doesn't really need to know about the two parameters, but I feel like we have to mention the defaults for them or not mention them at all.

Instead of what was pushed to the PR do think something like the following would be better?

With this update, when you specify BYO Knowledge information sources in OLSConfig.spec.ols.rag specification file specify the URL path for the image file.
+
.Example configuration
[source,yaml,subs="attributes,verbatim"]

spec:
ols:
rag:
- image: quay.io//my-byok-image:latest

Copy link

openshift-ci bot commented Jul 29, 2025

@rh-tokeefe: 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants