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.1
Red Hat OpenShift Lightspeed 1.0.1 is now available on OpenShift Container Platform 4.15 and later.
1.1.1. Enhancements
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.1.2. Known issues
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.2. OpenShift Lightspeed version 1.0
Red Hat OpenShift Lightspeed 1.0 is now available on OpenShift Container Platform 4.15 and later.
1.2.1. Enhancements
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.2.2. Known issues
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.