Chapter 1. OpenShift Lightspeed release notes

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 in Extra 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

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:

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

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

Previously, the indexPath and indexID parameters were required. Now they are optional. The default values for the parameters are /rag/vector_db and vector_db_index respectively.

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.

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.

This release includes the following Technology Preview features:

For OpenShift Container Platform 4.17 and later, the OpenShift Lightspeed icon disappears when you click Create Namespace or Create Project from one of the following locations in the OpenShift Container Platform web console:

Workaround: Refresh the web browser and the OpenShift Lightspeed icon appears. OLS-1815.

Changing the value of the quota parameter in the spec.ols.quotaHandlersConfig.limitersConfig specification of the OLSConfig custom resource file does not take effect until the currently defined quota period expires.

Workaround: Delete the OpenShift Lightspeed Operator. Ensure that any operand pods that the OpenShift Lightspeed Operator manages, and the Persistent Volume Claim lightspeed-postgres-pvc associated with the postgres pod are also deleted. Then, install the OpenShift Lightspeed Operator again. OLS-1826

After restarting the postgres pod, the OpenShift Lightspeed service pod fails to connect to the postgres pod.

Workaround: Restart the OpenShift Lightspeed service pod so that the service pod connects to the postgres pod. OLS-1835.