Repository: openshift/openshift-docs
Pull request #91414: OLS-1614: Release Notes for Lightspeed 0.3.3
Author: login: rh-tokeefe
Labels: name: peer-review-done
description: Signifies that the peer review team has reviewed this PR
name: size/M
description: Denotes a PR that changes 30-99 lines, ignoring generated files.
name: jira/valid-reference
description: Indicates that this PR references a valid Jira ticket of any type.
Created: 2025-04-01T13:14:10Z | Merged: 2025-04-15T17:43:39Z

Affects:
[lightspeed-main](https://github.com/openshift/openshift-docs/tree/lightspeed-docs-main)
[lightspeed-docs-1.0tp1](https://github.com/openshift/openshift-docs/tree/lightspeed-docs-1.0tp1)

This PR is part of the standalone doc set for the Lightspeed project. Kathryn is aware that this content applies for a product that is part of a Developer Preview release. The project is seeking feedback from early adopters.

PR must be CP'd back to the lightspeed-docs-1.0tp1 branch.

Version(s): TP

Issue: https://issues.redhat.com/browse/OLS-1614
<!--- Add a link to the Bugzilla, Jira, or GitHub issue, if applicable. --->

Link to docs preview:
https://91414--ocpdocs-pr.netlify.app/openshift-lightspeed/latest/release_notes/ols-release-notes.html#ols-0-3-3-release-notes_ols-release-notes
<!--- Add direct link(s) to the exact page(s) with updated content from the preview build. --->

QE review:
- [x] QE has approved this change.
<!--- QE approval is required to merge a PR except for changes that do not impact the meaning of the docs. --->

Additional information:
<!--- Optional: Include additional context or expand the description here.--->

<!--- After you open your PR, ask for review from the OpenShift docs team:
  For community authors: Tag @openshift/team-documentation in a GitHub comment.--->



Diff:
diff --git a/modules/ols-0-1-5-release-notes.adoc b/modules/ols-0-1-5-release-notes.adoc
index f0d2a60e2872..f94c4916e5a1 100644
--- a/modules/ols-0-1-5-release-notes.adoc
+++ b/modules/ols-0-1-5-release-notes.adoc
@@ -7,7 +7,7 @@
 
 Issued: 12 September 2024
 
-{ols-official} 0.1.5 is now available on {ocp-product-title} 4.15 or later.
+{ols-official} 0.1.5 is now available on {ocp-product-title} 4.15 and later.
 
 [id="ols-0-1-5-enhancements_{context}"]
 == Enhancements
diff --git a/modules/ols-0-1-6-release-notes.adoc b/modules/ols-0-1-6-release-notes.adoc
index 2014ea312cd2..587661bb55e4 100644
--- a/modules/ols-0-1-6-release-notes.adoc
+++ b/modules/ols-0-1-6-release-notes.adoc
@@ -5,7 +5,7 @@
 [id="ols-0-1-6-release-notes_{context}"]
 = {ols-long} version 0.1.6
 
-{ols-official} 0.1.6 is now available on {ocp-product-title} 4.15 or later.
+{ols-official} 0.1.6 is now available on {ocp-product-title} 4.15 and later.
 
 [id="ols-0-1-6-enhancements_{context}"]
 == Enhancements
diff --git a/modules/ols-0-1-7-release-notes.adoc b/modules/ols-0-1-7-release-notes.adoc
index 826850ed867a..1942e64ba7b7 100644
--- a/modules/ols-0-1-7-release-notes.adoc
+++ b/modules/ols-0-1-7-release-notes.adoc
@@ -5,7 +5,7 @@
 [id="ols-0-1-7-release-notes_{context}"]
 = {ols-long} version 0.1.7
 
-{ols-official} 0.1.7 is now available on {ocp-product-title} 4.15 or later.
+{ols-official} 0.1.7 is now available on {ocp-product-title} 4.15 and later.
 
 [id="ols-0-1-7-enhancements_{context}"]
 == Enhancements
diff --git a/modules/ols-0-2-0-release-notes.adoc b/modules/ols-0-2-0-release-notes.adoc
index 79f3bd75a702..8e8974e4c1bc 100644
--- a/modules/ols-0-2-0-release-notes.adoc
+++ b/modules/ols-0-2-0-release-notes.adoc
@@ -5,7 +5,7 @@
 [id="ols-0-2-0-release-notes_{context}"]
 = {ols-long} version 0.2.0
 
-{ols-official} 0.2.0 is now available on {ocp-product-title} 4.15 or later.
+{ols-official} 0.2.0 is now available on {ocp-product-title} 4.15 and later.
 
 [id="ols-0-2-2-enhancements_{context}"]
 == Enhancements
diff --git a/modules/ols-0-2-1-release-notes.adoc b/modules/ols-0-2-1-release-notes.adoc
index 46fd3aedf76c..bb76cbb2b960 100644
--- a/modules/ols-0-2-1-release-notes.adoc
+++ b/modules/ols-0-2-1-release-notes.adoc
@@ -5,7 +5,7 @@
 [id="ols-0-2-1-release-notes_{context}"]
 = {ols-long} version 0.2.1
 
-{ols-official} 0.2.1 is now available on {ocp-product-title} 4.15 or later.
+{ols-official} 0.2.1 is now available on {ocp-product-title} 4.15 and later.
 
 [id="ols-0-2-1-enhancements_{context}"]
 == Enhancements
diff --git a/modules/ols-0-3-0-release-notes.adoc b/modules/ols-0-3-0-release-notes.adoc
index 2fd275020baa..e6d23bc70e54 100644
--- a/modules/ols-0-3-0-release-notes.adoc
+++ b/modules/ols-0-3-0-release-notes.adoc
@@ -5,11 +5,11 @@
 [id="ols-0-3-0-release-notes_{context}"]
 = {ols-long} version 0.3.0
 
-{ols-official} 0.3.0 is now available on {ocp-product-title} 4.15 or later.
+{ols-official} 0.3.0 is now available on {ocp-product-title} 4.15 and later.
 
 [IMPORTANT]
 ====
-{ols-official} is designed for FIPS. When running on {ocp-product-title} in FIPS mode, it uses the {rhel} cryptographic libraries submitted (or planned to be submitted) to NIST for FIPS validation on only the `x86_64`, `ppc64le`, and `s390X` architectures. For more information about the NIST validation program, see link:https://csrc.nist.gov/Projects/cryptographic-module-validation-program/validated-modules[Cryptographic Module Validation Program]. For the latest NIST status of the individual versions of {rhel} cryptographic libraries that have been submitted for validation, see link:https://access.redhat.com/articles/compliance_activities_and_gov_standards#fips-140-2-and-fips-140-3-2[Compliance Activities and Government Standards].
+{ols-official} is designed for Federal Information Processing Standards (FIPS). When running on {ocp-product-title} in FIPS mode, it uses the {rhel} cryptographic libraries submitted (or planned to be submitted) to NIST for FIPS validation on only the `x86_64`, `ppc64le`, and `s390X` architectures. For more information about the NIST validation program, see link:https://csrc.nist.gov/Projects/cryptographic-module-validation-program/validated-modules[Cryptographic Module Validation Program]. For the latest NIST status of the individual versions of {rhel} cryptographic libraries that have been submitted for validation, see link:https://access.redhat.com/articles/compliance_activities_and_gov_standards#fips-140-2-and-fips-140-3-2[Compliance Activities and Government Standards].
 ====
 
 [id="ols-0-3-0-enhancements_{context}"]
diff --git a/modules/ols-0-3-1-release-notes.adoc b/modules/ols-0-3-1-release-notes.adoc
index f7bef813bbc0..2c18f4f41121 100644
--- a/modules/ols-0-3-1-release-notes.adoc
+++ b/modules/ols-0-3-1-release-notes.adoc
@@ -5,11 +5,11 @@
 [id="ols-0-3-1-release-notes_{context}"]
 = {ols-long} version 0.3.1
 
-{ols-official} 0.3.1 is now available on {ocp-product-title} 4.15 or later.
+{ols-official} 0.3.1 is now available on {ocp-product-title} 4.15 and later.
 
 [IMPORTANT]
 ====
-{ols-official} is designed for FIPS. When running on {ocp-product-title} in FIPS mode, it uses the {rhel} cryptographic libraries submitted (or planned to be submitted) to NIST for FIPS validation on only the `x86_64`, `ppc64le`, and `s390X` architectures. For more information about the NIST validation program, see link:https://csrc.nist.gov/Projects/cryptographic-module-validation-program/validated-modules[Cryptographic Module Validation Program]. For the latest NIST status of the individual versions of {rhel} cryptographic libraries that have been submitted for validation, see link:https://access.redhat.com/articles/compliance_activities_and_gov_standards#fips-140-2-and-fips-140-3-2[Compliance Activities and Government Standards].
+{ols-official} is designed for Federal Information Processing Standards (FIPS). When running on {ocp-product-title} in FIPS mode, it uses the {rhel} cryptographic libraries submitted (or planned to be submitted) to NIST for FIPS validation on only the `x86_64`, `ppc64le`, and `s390X` architectures. For more information about the NIST validation program, see link:https://csrc.nist.gov/Projects/cryptographic-module-validation-program/validated-modules[Cryptographic Module Validation Program]. For the latest NIST status of the individual versions of {rhel} cryptographic libraries that have been submitted for validation, see link:https://access.redhat.com/articles/compliance_activities_and_gov_standards#fips-140-2-and-fips-140-3-2[Compliance Activities and Government Standards].
 ====
 
 [id="ols-0-3-1-enhancements_{context}"]
diff --git a/modules/ols-0-3-2-release-notes.adoc b/modules/ols-0-3-2-release-notes.adoc
index 8c79326ca226..72a83cd4d8fc 100644
--- a/modules/ols-0-3-2-release-notes.adoc
+++ b/modules/ols-0-3-2-release-notes.adoc
@@ -5,11 +5,11 @@
 [id="ols-0-3-2-release-notes_{context}"]
 = {ols-long} version 0.3.2
 
-{ols-official} 0.3.2 is now available on {ocp-product-title} 4.15 or later.
+{ols-official} 0.3.2 is now available on {ocp-product-title} 4.15 and later.
 
 [IMPORTANT]
 ====
-{ols-official} is designed for FIPS. When running on {ocp-product-title} in FIPS mode, it uses the {rhel} cryptographic libraries submitted (or planned to be submitted) to NIST for FIPS validation on only the `x86_64`, `ppc64le`, and `s390X` architectures. For more information about the NIST validation program, see link:https://csrc.nist.gov/Projects/cryptographic-module-validation-program/validated-modules[Cryptographic Module Validation Program]. For the latest NIST status of the individual versions of {rhel} cryptographic libraries that have been submitted for validation, see link:https://access.redhat.com/articles/compliance_activities_and_gov_standards#fips-140-2-and-fips-140-3-2[Compliance Activities and Government Standards].
+{ols-official} is designed for Federal Information Processing Standards (FIPS). When running on {ocp-product-title} in FIPS mode, it uses the {rhel} cryptographic libraries submitted (or planned to be submitted) to NIST for FIPS validation on only the `x86_64`, `ppc64le`, and `s390X` architectures. For more information about the NIST validation program, see link:https://csrc.nist.gov/Projects/cryptographic-module-validation-program/validated-modules[Cryptographic Module Validation Program]. For the latest NIST status of the individual versions of {rhel} cryptographic libraries that have been submitted for validation, see link:https://access.redhat.com/articles/compliance_activities_and_gov_standards#fips-140-2-and-fips-140-3-2[Compliance Activities and Government Standards].
 ====
 
 [id="ols-0-3-2-enhancements_{context}"]
diff --git a/modules/ols-0-3-3-fixed-issues.adoc b/modules/ols-0-3-3-fixed-issues.adoc
new file mode 100644
index 000000000000..70f77e13f4fb
--- /dev/null
+++ b/modules/ols-0-3-3-fixed-issues.adoc
@@ -0,0 +1,11 @@
+// This module is used in the following assemblies:
+
+// * lightspeed-docs-main/release_notes/ols-release-notes.adoc
+
+:_mod-docs-content-type: REFERENCE
+[id="ols-0-3-3-fixed-issues_{context}"]
+= Fixed issues
+
+The following issues are fixed with {ols-official} 0.3.3:
+
+* Previously, the {ols-long} Operator would attempt to reconcile the {ols-long} Service even when the API token key was missing. The Service did not start, and no error was generated. Now, the {ols-long} Operator checks that the secret holding the API token for the large language model (LLM) provider contains the `apitoken` key before reconciling the Service. If the token key is missing, the Operator generates an error message in the `status` field of the `OLSConfig` custom resource file. link:https://issues.redhat.com/browse/OLS-1449[OLS-1449].
\ No newline at end of file
diff --git a/modules/ols-0-3-3-release-notes.adoc b/modules/ols-0-3-3-release-notes.adoc
new file mode 100644
index 000000000000..2856894d2631
--- /dev/null
+++ b/modules/ols-0-3-3-release-notes.adoc
@@ -0,0 +1,22 @@
+// Module included in the following assemblies:
+// * lightspeed-docs-main/release_notes/ols-release-notes.adoc
+
+:_mod-docs-content-type: REFERENCE
+[id="ols-0-3-3-release-notes_{context}"]
+= {ols-long} version 0.3.3
+
+{ols-official} 0.3.3 is now available on {ocp-product-title} 4.15 and later.
+
+[IMPORTANT]
+====
+{ols-official} is designed for Federal Information Processing Standards (FIPS). When running on {ocp-product-title} in FIPS mode, it uses the {rhel} cryptographic libraries submitted (or planned to be submitted) to NIST for FIPS validation on only the `x86_64`, `ppc64le`, and `s390X` architectures. For more information about the NIST validation program, see link:https://csrc.nist.gov/Projects/cryptographic-module-validation-program/validated-modules[Cryptographic Module Validation Program]. For the latest NIST status of the individual versions of {rhel} cryptographic libraries that have been submitted for validation, see link:https://access.redhat.com/articles/compliance_activities_and_gov_standards#fips-140-2-and-fips-140-3-2[Compliance Activities and Government Standards].
+====
+
+[id="ols-0-3-3-enhancements_{context}"]
+== Enhancements
+
+The following enhancements are made with {ols-official} 0.3.3:
+
+* This release adds the ability to upload YAML files from your computer. You can attach a YAML file for any {k8s} resource to the prompt you send to the {ols-long} Service. Adding the file to the prompt provides additional context when the Service generates an answer.
+
+* This release adds a PostgreSQL database as the conversation cache. The conversation cache present in the PostgeSQL database is not backed up in the file system so the conversation cache is lost if the PostgreSQL pod restarts.
diff --git a/release_notes/ols-release-notes.adoc b/release_notes/ols-release-notes.adoc
index 6783c4eade62..6fbe8f8b3d02 100644
--- a/release_notes/ols-release-notes.adoc
+++ b/release_notes/ols-release-notes.adoc
@@ -8,6 +8,8 @@ toc::[]
 
 The release notes highlight what is new and what has changed with each {ols-official} release.
 
+include::modules/ols-0-3-3-release-notes.adoc[leveloffset=+1]
+include::modules/ols-0-3-3-fixed-issues.adoc[leveloffset=+2]
 include::modules/ols-0-3-2-release-notes.adoc[leveloffset=+1]
 include::modules/ols-0-3-2-fixed-issues.adoc[leveloffset=+2]
 include::modules/ols-0-3-1-release-notes.adoc[leveloffset=+1]


Reviews:
user: login: xenolinux
body: 2 comments; lgtm
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-15T06:39:35Z
user: login: xenolinux
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-15T06:41:15Z
user: login: rh-tokeefe
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-15T11:58:46Z
user: login: rh-tokeefe
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-15T12:40:05Z
user: login: skopacz1
body: Merge review LGTM!
state: APPROVED
author_association: CONTRIBUTOR
submitted_at: 2025-04-15T17:43:26Z

Review comments:
diff_hunk: @@ -0,0 +1,22 @@
+// Module included in the following assemblies:
+// * lightspeed-docs-main/release_notes/ols-release-notes.adoc
+
+:_mod-docs-content-type: REFERENCE
+[id="ols-0-3-3-release-notes_{context}"]
+= {ols-long} version 0.3.3
+
+{ols-official} 0.3.3 is now available on {ocp-product-title} 4.15 or later.
path: modules/ols-0-3-3-release-notes.adoc
user: login: xenolinux
body: ```suggestion
{ols-official} 0.3.3 is now available on {ocp-product-title} 4.15 and later.
```


IMO when specifying the availability, "and" is clearer. But I noticed in the preview that "or" is used consistently. So up to you!

created_at: 2025-04-15T06:33:19Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,22 @@
+// Module included in the following assemblies:
+// * lightspeed-docs-main/release_notes/ols-release-notes.adoc
+
+:_mod-docs-content-type: REFERENCE
+[id="ols-0-3-3-release-notes_{context}"]
+= {ols-long} version 0.3.3
+
+{ols-official} 0.3.3 is now available on {ocp-product-title} 4.15 or later.
+
+[IMPORTANT]
+====
+{ols-official} is designed for FIPS. When running on {ocp-product-title} in FIPS mode, it uses the {rhel} cryptographic libraries submitted (or planned to be submitted) to NIST for FIPS validation on only the `x86_64`, `ppc64le`, and `s390X` architectures. For more information about the NIST validation program, see link:https://csrc.nist.gov/Projects/cryptographic-module-validation-program/validated-modules[Cryptographic Module Validation Program]. For the latest NIST status of the individual versions of {rhel} cryptographic libraries that have been submitted for validation, see link:https://access.redhat.com/articles/compliance_activities_and_gov_standards#fips-140-2-and-fips-140-3-2[Compliance Activities and Government Standards].
path: modules/ols-0-3-3-release-notes.adoc
user: login: xenolinux
body: ```suggestion
{ols-official} is designed for Federal Information Processing Standards (FIPS). When running on {ocp-product-title} in FIPS mode, it uses the {rhel} cryptographic libraries submitted (or planned to be submitted) to NIST for FIPS validation on only the `x86_64`, `ppc64le`, and `s390X` architectures. For more information about the NIST validation program, see link:https://csrc.nist.gov/Projects/cryptographic-module-validation-program/validated-modules[Cryptographic Module Validation Program]. For the latest NIST status of the individual versions of {rhel} cryptographic libraries that have been submitted for validation, see link:https://access.redhat.com/articles/compliance_activities_and_gov_standards#fips-140-2-and-fips-140-3-2[Compliance Activities and Government Standards].
```
created_at: 2025-04-15T06:36:34Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,22 @@
+// Module included in the following assemblies:
+// * lightspeed-docs-main/release_notes/ols-release-notes.adoc
+
+:_mod-docs-content-type: REFERENCE
+[id="ols-0-3-3-release-notes_{context}"]
+= {ols-long} version 0.3.3
+
+{ols-official} 0.3.3 is now available on {ocp-product-title} 4.15 or later.
path: modules/ols-0-3-3-release-notes.adoc
user: login: xenolinux
body: If you go with "and", you might want to update other similar instances of "or" too.
created_at: 2025-04-15T06:41:15Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,22 @@
+// Module included in the following assemblies:
+// * lightspeed-docs-main/release_notes/ols-release-notes.adoc
+
+:_mod-docs-content-type: REFERENCE
+[id="ols-0-3-3-release-notes_{context}"]
+= {ols-long} version 0.3.3
+
+{ols-official} 0.3.3 is now available on {ocp-product-title} 4.15 or later.
+
+[IMPORTANT]
+====
+{ols-official} is designed for FIPS. When running on {ocp-product-title} in FIPS mode, it uses the {rhel} cryptographic libraries submitted (or planned to be submitted) to NIST for FIPS validation on only the `x86_64`, `ppc64le`, and `s390X` architectures. For more information about the NIST validation program, see link:https://csrc.nist.gov/Projects/cryptographic-module-validation-program/validated-modules[Cryptographic Module Validation Program]. For the latest NIST status of the individual versions of {rhel} cryptographic libraries that have been submitted for validation, see link:https://access.redhat.com/articles/compliance_activities_and_gov_standards#fips-140-2-and-fips-140-3-2[Compliance Activities and Government Standards].
path: modules/ols-0-3-3-release-notes.adoc
user: login: rh-tokeefe
body: The FIPS language was previously vetted through marketing and legal, and I was under the impression we were not supposed to make changes.  I wrote out first instance here because I think it's a good suggestion. Thanks!
created_at: 2025-04-15T11:58:46Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,22 @@
+// Module included in the following assemblies:
+// * lightspeed-docs-main/release_notes/ols-release-notes.adoc
+
+:_mod-docs-content-type: REFERENCE
+[id="ols-0-3-3-release-notes_{context}"]
+= {ols-long} version 0.3.3
+
+{ols-official} 0.3.3 is now available on {ocp-product-title} 4.15 or later.
path: modules/ols-0-3-3-release-notes.adoc
user: login: rh-tokeefe
body: Done
created_at: 2025-04-15T12:40:04Z
author_association: CONTRIBUTOR

PR comments:
user: login: openshift-ci-robot
created_at: 2025-04-01T13:14:15Z
body: @rh-tokeefe: This pull request references [OLS-1614](https://issues.redhat.com//browse/OLS-1614) which is a valid jira issue.

<details>

In response to [this](https://github.com/openshift/openshift-docs/pull/91414):

><!--- PR title format: [GH#<gh-issue-id>][BZ#<bz-issue-id>][OCPBUGS#<jira-issue-id>][OSDOCS#<jira-issue-id>]: <short-description-of-the-pr> --->
>
><!--- If your changes apply to the latest release and/or in-development version of OpenShift, open your PR against the `main` branch.
>Do not create or rename a top-level directory (or any subdirectory in a directory that contains a hugebook.flag file) in the repository and topic map without checking with a docs program manager first.
>If a book is being created or modified, there are changes on the Customer Portal that must also be made.
>
>* For more details about the information requested in this template, see:
>  https://github.com/openshift/openshift-docs/blob/main/contributing_to_docs/create_or_edit_content.adoc#submit-PR --->
>
>Version(s):
><!--- Specify the version or versions of OpenShift your PR applies to. -->
>
>Issue:
><!--- Add a link to the Bugzilla, Jira, or GitHub issue, if applicable. --->
>
>Link to docs preview:
><!--- Add direct link(s) to the exact page(s) with updated content from the preview build. --->
>
>QE review:
>- [ ] QE has approved this change.
><!--- QE approval is required to merge a PR except for changes that do not impact the meaning of the docs. --->
>
>Additional information:
><!--- Optional: Include additional context or expand the description here.--->
>
><!--- After you open your PR, ask for review from the OpenShift docs team:
>  For community authors: Tag @openshift/team-documentation in a GitHub comment.--->
>


Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fopenshift-docs).  If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
</details>
author_association: NONE
user: login: openshift-ci-robot
created_at: 2025-04-01T13:17:50Z
body: @rh-tokeefe: This pull request references [OLS-1614](https://issues.redhat.com//browse/OLS-1614) which is a valid jira issue.

<details>

In response to [this](https://github.com/openshift/openshift-docs/pull/91414):

>Affects:
>[lightspeed-main](https://github.com/openshift/openshift-docs/tree/lightspeed-docs-main)
>[lightspeed-docs-1.0tp1](https://github.com/openshift/openshift-docs/tree/lightspeed-docs-1.0tp1)
>
>This PR is part of the standalone doc set for the Lightspeed project. Kathryn is aware that this content applies for a product that is part of a Developer Preview release. The project is seeking feedback from early adopters.
>
>PR must be CP'd back to the lightspeed-docs-1.0tp1 branch.
>
>Version(s): TP
>
>Issue: https://issues.redhat.com/browse/OLS-1614
><!--- Add a link to the Bugzilla, Jira, or GitHub issue, if applicable. --->
>
>Link to docs preview:
><!--- Add direct link(s) to the exact page(s) with updated content from the preview build. --->
>
>QE review:
>- [ ] QE has approved this change.
><!--- QE approval is required to merge a PR except for changes that do not impact the meaning of the docs. --->
>
>Additional information:
><!--- Optional: Include additional context or expand the description here.--->
>
><!--- After you open your PR, ask for review from the OpenShift docs team:
>  For community authors: Tag @openshift/team-documentation in a GitHub comment.--->
>


Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fopenshift-docs).  If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
</details>
author_association: NONE
user: login: ocpdocs-previewbot
created_at: 2025-04-01T13:35:20Z
body: 🤖 Tue Apr 15 12:35:12 - Prow CI generated the docs preview:

https://91414--ocpdocs-pr.netlify.app/openshift-lightspeed/latest/release_notes/ols-release-notes.html
author_association: NONE
user: login: openshift-ci-robot
created_at: 2025-04-02T13:54:44Z
body: @rh-tokeefe: This pull request references [OLS-1614](https://issues.redhat.com//browse/OLS-1614) which is a valid jira issue.

<details>

In response to [this](https://github.com/openshift/openshift-docs/pull/91414):

>Affects:
>[lightspeed-main](https://github.com/openshift/openshift-docs/tree/lightspeed-docs-main)
>[lightspeed-docs-1.0tp1](https://github.com/openshift/openshift-docs/tree/lightspeed-docs-1.0tp1)
>
>This PR is part of the standalone doc set for the Lightspeed project. Kathryn is aware that this content applies for a product that is part of a Developer Preview release. The project is seeking feedback from early adopters.
>
>PR must be CP'd back to the lightspeed-docs-1.0tp1 branch.
>
>Version(s): TP
>
>Issue: https://issues.redhat.com/browse/OLS-1614
><!--- Add a link to the Bugzilla, Jira, or GitHub issue, if applicable. --->
>
>Link to docs preview:
>https://91414--ocpdocs-pr.netlify.app/openshift-lightspeed/latest/release_notes/ols-release-notes.html#ols-0-3-3-release-notes_ols-release-notes
><!--- Add direct link(s) to the exact page(s) with updated content from the preview build. --->
>
>QE review:
>- [ ] QE has approved this change.
><!--- QE approval is required to merge a PR except for changes that do not impact the meaning of the docs. --->
>
>Additional information:
><!--- Optional: Include additional context or expand the description here.--->
>
><!--- After you open your PR, ask for review from the OpenShift docs team:
>  For community authors: Tag @openshift/team-documentation in a GitHub comment.--->
>


Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fopenshift-docs).  If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
</details>
author_association: NONE
user: login: JoaoFula
created_at: 2025-04-14T11:54:43Z
body: LGTM
author_association: CONTRIBUTOR
user: login: openshift-ci-robot
created_at: 2025-04-14T13:53:00Z
body: @rh-tokeefe: This pull request references [OLS-1614](https://issues.redhat.com//browse/OLS-1614) which is a valid jira issue.

<details>

In response to [this](https://github.com/openshift/openshift-docs/pull/91414):

>Affects:
>[lightspeed-main](https://github.com/openshift/openshift-docs/tree/lightspeed-docs-main)
>[lightspeed-docs-1.0tp1](https://github.com/openshift/openshift-docs/tree/lightspeed-docs-1.0tp1)
>
>This PR is part of the standalone doc set for the Lightspeed project. Kathryn is aware that this content applies for a product that is part of a Developer Preview release. The project is seeking feedback from early adopters.
>
>PR must be CP'd back to the lightspeed-docs-1.0tp1 branch.
>
>Version(s): TP
>
>Issue: https://issues.redhat.com/browse/OLS-1614
><!--- Add a link to the Bugzilla, Jira, or GitHub issue, if applicable. --->
>
>Link to docs preview:
>https://91414--ocpdocs-pr.netlify.app/openshift-lightspeed/latest/release_notes/ols-release-notes.html#ols-0-3-3-release-notes_ols-release-notes
><!--- Add direct link(s) to the exact page(s) with updated content from the preview build. --->
>
>QE review:
>- [x] QE has approved this change.
><!--- QE approval is required to merge a PR except for changes that do not impact the meaning of the docs. --->
>
>Additional information:
><!--- Optional: Include additional context or expand the description here.--->
>
><!--- After you open your PR, ask for review from the OpenShift docs team:
>  For community authors: Tag @openshift/team-documentation in a GitHub comment.--->
>


Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fopenshift-docs).  If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
</details>
author_association: NONE
user: login: raptorsun
created_at: 2025-04-14T14:05:13Z
body: /lgtm
author_association: NONE
user: login: rh-tokeefe
created_at: 2025-04-14T14:14:10Z
body: /label peer-review-needed
author_association: CONTRIBUTOR
user: login: xrajesh
created_at: 2025-04-14T19:27:48Z
body: /lgtm

author_association: NONE
user: login: openshift-ci[bot]
created_at: 2025-04-14T19:29:27Z
body: New changes are detected. LGTM label has been removed.
author_association: NONE
user: login: openshift-ci[bot]
created_at: 2025-04-15T12:38:02Z
body: @rh-tokeefe: all tests **passed!**


[Full PR test history](https://prow.ci.openshift.org/pr-history?org=openshift&repo=openshift-docs&pr=91414). [Your PR dashboard](https://prow.ci.openshift.org/pr?query=is:pr+state:open+author:rh-tokeefe).

<details>

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).
</details>
<!-- test report -->
author_association: NONE
user: login: rh-tokeefe
created_at: 2025-04-15T12:40:13Z
body: /label merge-review-needed
author_association: CONTRIBUTOR
user: login: skopacz1
created_at: 2025-04-15T17:43:46Z
body: /cherrypick lightspeed-docs-1.0tp1
author_association: CONTRIBUTOR
user: login: openshift-cherrypick-robot
created_at: 2025-04-15T17:44:47Z
body: @skopacz1: new pull request created: #92221

<details>

In response to [this](https://github.com/openshift/openshift-docs/pull/91414#issuecomment-2807003299):

>/cherrypick lightspeed-docs-1.0tp1


Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
</details>
author_association: NONE