Chapter 1. OpenShift Lightspeed release notes
The release notes highlight what is new and what has changed with each Red Hat OpenShift Lightspeed release.
Red Hat OpenShift Lightspeed is designed for Federal Information Processing Standards (FIPS). When running on OpenShift Container Platform in FIPS mode, it uses the Red Hat Enterprise Linux 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 Cryptographic Module Validation Program. For the latest NIST status of the individual versions of Red Hat Enterprise Linux cryptographic libraries that have been submitted for validation, see Product compliance.
1.1. OpenShift Lightspeed version 1.0.5 Copy linkLink copied to clipboard!
Red Hat OpenShift Lightspeed 1.0.5 is now available on OpenShift Container Platform 4.16 and later.
1.1.1. Enhancements Copy linkLink copied to clipboard!
Red Hat OpenShift Lightspeed 1.0.5 provides the following enhancements:
- This release makes Red Hat OpenShift Lightspeed 1.0.5 generally available, and is supported on OpenShift Container Platform 4.16 and later.
-
With this release, you can attach
cron job
logs to the question you submit to Red Hat OpenShift Lightspeed, enabling the Service to provide more context-aware troubleshooting, diagnostics, and analysis of automated job outcomes, errors, or irregular behaviors.
1.1.2. Fixed issues Copy linkLink copied to clipboard!
Red Hat OpenShift Lightspeed 1.0.5 fixes the following issues:
Before this update, Red Hat OpenShift Lightspeed failed to use the GPT-5 model, and OpenAI generated an Error code: 400
error message. With this release, Red Hat OpenShift Lightspeed supports the GPT-5 model. OLS-2041
1.2. OpenShift Lightspeed version 1.0.4 Copy linkLink copied to clipboard!
Red Hat OpenShift Lightspeed 1.0.4 is now available on OpenShift Container Platform 4.16 and later.
1.2.1. Enhancements Copy linkLink copied to clipboard!
Red Hat OpenShift Lightspeed 1.0.4 provides the following enhancements:
- This release makes Red Hat OpenShift Lightspeed 1.0.4 generally available, and is supported on OpenShift Container Platform 4.16 and later.
- The cluster interaction Technology Preview feature now uses the Model Context Protocol (MCP). MCP is an open protocol that standardizes how applications provide context to large language models (LLMs). Using the protocol, an MCP server offers a standardized way for an LLM to increase context by requesting and receiving real-time information from external resources.
1.2.2. Fixed issues Copy linkLink copied to clipboard!
Red Hat OpenShift Lightspeed 1.0.4 fixes the following issues:
Before this update, the OpenShift Lightspeed Service incorrectly rejected the
api_version
parameter for Microsoft Azure OpenAI providers, despite it being officially supported. This resulted inExtra inputs are not permitted
errors during API calls.This release fixes the Microsoft Azure OpenAI API version validation issue in the OpenShift Lightspeed Service, which now allows for correct parameter usage and eliminates the error. OLS-1973
1.3. OpenShift Lightspeed version 1.0.3 Copy linkLink copied to clipboard!
Red Hat OpenShift Lightspeed 1.0.3 is now available on OpenShift Container Platform 4.15 and later.
1.3.1. Enhancements Copy linkLink copied to clipboard!
The following enhancements are made with Red Hat OpenShift Lightspeed 1.0.3:
- This release makes Red Hat OpenShift Lightspeed 1.0.3 generally available, and is supported on OpenShift Container Platform 4.15 and later.
With this update, when you specify BYO Knowledge information sources in
OLSConfig.spec.ols.rag
specification file you only have to specify the URL path for the image.The custom resource (CR) uses the following default settings:
Example configuration
spec: ols: rag: - image: quay.io/<username>/my-byok-image:latest
spec: ols: rag: - image: quay.io/<username>/my-byok-image:latest
1 Copy to Clipboard Copied! Toggle word wrap Toggle overflow - 1
- Where
image
specifies the tag for the image that was pushed to the image registry so that the OpenShift Lightspeed Operator can access the custom content. The OpenShift Lightspeed Operator can work with more than one RAG database that you create.
Previously, the
indexPath
andindexID
parameters were required. Now they are optional. The default values for the parameters are/rag/vector_db
andvector_db_index
respectively.
1.3.2. Fixed issues Copy linkLink copied to clipboard!
The following issues are fixed with Red Hat OpenShift Lightspeed 1.0.3:
-
Before this update, the OpenShift Lightspeed service could not reload BYO Knowledge images with floating tags. This condition occurred even after a restart because the
ImagePullPolicy
parameter was hardcoded toPullIfNotPresent
. As a result, BYO Knowledge images failed to reload from the container registry, causing users to experience stale images. With this update, when the OpenShift Lightspeed service restarts, it pulls the BYO Knowledge images from the container registry, ensuring consistent access to BYO Knowledge images. OLS-1956.
1.4. OpenShift Lightspeed version 1.0.2 Copy linkLink copied to clipboard!
Red Hat OpenShift Lightspeed 1.0.2 is now available on OpenShift Container Platform 4.15 and later.
1.4.1. Enhancements Copy linkLink copied to clipboard!
The following enhancements are made with Red Hat OpenShift Lightspeed 1.0.2:
- This release makes Red Hat OpenShift Lightspeed 1.0.2 generally available, and is supported on OpenShift Container Platform 4.15 and later.
1.4.2. Fixed issues Copy linkLink copied to clipboard!
The following issues are fixed with Red Hat OpenShift Lightspeed 1.0.2:
-
Before this update, the cluster-wide proxy incorrectly routed large language model (LLM) provider connections, ignoring the
no_proxy
environment variable. This led to end users experiencing OpenShift Lightspeed attempting to connect to the LLM provider through a proxy when theno_proxy
variable was explicitly defined. In this release, Lightspeed now respects theno_proxy
environment variable for LLM provider connections. As a result, Lightspeed ignores proxy settings whenno_proxy
is set, enhancing direct LLM provider connections. OLS-1861.
1.5. OpenShift Lightspeed version 1.0.1 Copy linkLink copied to clipboard!
Red Hat OpenShift Lightspeed 1.0.1 is now available on OpenShift Container Platform 4.15 and later.
1.5.1. Enhancements Copy linkLink copied to clipboard!
The following enhancements are made with Red Hat OpenShift Lightspeed 1.0.1:
- This release makes Red Hat OpenShift Lightspeed 1.0.1 generally available, and is supported on OpenShift Container Platform 4.15 and later.
This release introduces the BYO Knowledge tool as a Technology Preview feature. You can use this tool to add your own custom content as a knowledge source so that a large language model (LLM) can make use of information that is unique to your environment. By using this information, the tool creates a retrieval-augmented generation (RAG) database to enhance the knowledge that is available to the LLM.
ImportantThe BYO Knowledge tool is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.
For more information about the support scope of Red Hat Technology Preview features, see Technology Preview Features Support Scope.
1.5.2. Known issues Copy linkLink copied to clipboard!
The following issues are identified with Red Hat OpenShift Lightspeed 1.0.1:
If the OpenShift Container Platform cluster has a cluster-wide proxy and the
no_proxy
environment variable is set, the OpenShift Lightspeed service tries to connect to the large language model (LLM) provider through the proxy. OLS-1861.Workaround: None.
1.6. OpenShift Lightspeed version 1.0 Copy linkLink copied to clipboard!
Red Hat OpenShift Lightspeed 1.0 is now available on OpenShift Container Platform 4.15 and later.
1.6.1. Enhancements Copy linkLink copied to clipboard!
The following enhancements are made with Red Hat OpenShift Lightspeed 1.0:
- This release makes Red Hat OpenShift Lightspeed 1.0 generally available, adds new features, addresses Common Vulnerabilities and Exposures (CVEs), and is supported on OpenShift Container Platform 4.15 and later.
This release includes the following Technology Preview features:
- Cluster interaction
- PostgreSQL persistence
- Token quota
ImportantTechnology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.
For more information about the support scope of Red Hat Technology Preview features, see Technology Preview Features Support Scope.
1.6.2. Known issues Copy linkLink copied to clipboard!
The following issues are identified with Red Hat OpenShift Lightspeed 1.0:
For OpenShift Container Platform 4.17 and later, the Lightspeed icon disappears when you click Create Namespace or Create Project from one of the following locations in the OpenShift Container Platform web console:
-
Administration
Namespaces -
Home
Projects Create Project - The Project drop-down menu located at the top of most pages
Workaround: Refresh the web browser and the Lightspeed icon appears. OLS-1815.
-
Administration
Changing the value of the
quota
parameter in thespec.ols.quotaHandlersConfig.limitersConfig
specification of theOLSConfig
custom resource file does not take effect until the currently defined quota period expires.Workaround: Delete the Lightspeed Operator. Ensure that any operand pods that the Lightspeed Operator manages, and the Persistent Volume Claim
lightspeed-postgres-pvc
associated with thepostgres
pod are also deleted. Then, install the Lightspeed Operator again. OLS-1826After restarting the
postgres
pod, the Lightspeed service pod fails to connect to thepostgres
pod.Workaround: Restart the Lightspeed service pod so that the service pod connects to the
postgres
pod. OLS-1835.