About OpenShift Lightspeed
The following topics provide an overview of {ols-official} and discuss functional requirements.
OpenShift Lightspeed Overview
Red Hat OpenShift Lightspeed is a generative AI-powered virtual assistant for OpenShift Container Platform. Lightspeed functionality uses a natural-language interface in the OpenShift web console.
This early access program exists so that customers can provide feedback on the user experience, features and capabilities, issues encountered, and any other aspects of the product so that Lightspeed can become more aligned with your needs when it is released and made generally available.
OpenShift Requirements
OpenShift Lightspeed requires OpenShift Container Platform 4.15 or later running on x86 hardware. Any installation type or deployment architecture is supported so long as the cluster is 4.15+ and x86-based.
For the OpenShift Lightspeed Developer Preview release, the cluster you use must be connected to the Internet and it must have telemetry enabled. Telemetry is enabled by default. If you are using a standard installation process for OpenShift confirm that it does not disable telemetry.
Large Language Model (LLM) requirements
As part of the Developer Preview release, OpenShift Lightspeed relies on Software as a Service (SaaS) LLM providers. You will need to have either a trial or paid subscription that allows for API access to completions and inferences with one of the following providers:
-
OpenAI
-
Azure OpenAI
-
WatsonX
|
Many self-hosted or self-managed model servers claim API compatibility with OpenAI. It is possible to configure the OpenShift Lightspeed OpenAI provider to point to an API-compatible model server. If the model server is truly API-compatible, especially with respect to authentication, then it may work. These configurations have not been tested by Red Hat, and issues related to their use are outside the scope of Developer Preview support. |
About OpenAI
To use OpenAI with Red Hat OpenShift Lightspeed, you will need access to the OpenAI API platform.
About Azure OpenAI
To use Microsoft Azure with Red Hat OpenShift Lightspeed, you must have access to Microsoft Azure OpenAI.
About WatsonX
To use IBM WatsonX with Red Hat OpenShift Lightspeed, you will need an account with IBM Cloud’s WatsonX.
About data use
Red Hat OpenShift Lightspeed is a virtual assistant you interact with using natural language. Using the OpenShift Lightspeed interface, you send chat messages that OpenShift Lightspeed transforms and sends to the Large Language Model (LLM) provider you have configured for your environment. These messages can contain information about your cluster, cluster resources, or other aspects of your environment.
The OpenShift Lightspeed Developer Preview release has limited capabilities to filter or redact the information you provide to the LLM. Do not enter information into the OpenShift Lightspeed interface that you do not want to send to the LLM provider.
By using the OpenShift Lightspeed as part of the Developer Preview release, you agree that Red Hat may use all of the messages that you exchange with the LLM provider for any purpose. The transcript recording data uses the Red Hat Insights system’s back-end, and is subject to the same access restrictions and other security policies.
You may email Red Hat and request that your data be deleted at the end of the Developer Preview release period.
About data, telemetry, transcript, and feedback collection
OpenShift Lightspeed is a virtual assistant that you interact with using natural language. Communicating with OpenShift Lightspeed involves sending chat messages, which may include information about your cluster, your cluster resources, or other aspects of your environment. These messages are sent to OpenShift Lightspeed, potentially with some content filtered or redacted, and then sent to the LLM provider that you have configured.
Do not enter any information into the OpenShift Lightspeed user interface that you do not want sent to the LLM provider.
The transcript recording data uses the Red Hat Insights system back-end and is subject to the same access restrictions and other security policies described in Red Hat Insights data and application security.
About remote health monitoring
Red Hat records basic information using the Telemeter Client and the Insights Operator, which is generally referred to as Remote Health Monitoring in OpenShift clusters. The OpenShift documentation for remote health monitoring explains data collection and includes instructions for opting out. If you wish to disable transcript or feedback collection, you must follow the procedure for opting out of remote health monitoring. For more information, see "About remote health monitoring" in the OpenShift Container Platform documentation.
Transcript collection overview
Transcripts are sent to Red Hat every two hours, by default. If you are using the filtering and redaction functionality, the filtered or redacted content is sent to Red Hat. Red Hat does not see the original non-redacted content, and the redaction takes place before any content is captured in logs.
OpenShift Lightspeed temporarily logs and stores complete transcripts of conversations that users have with the virtual assistant. This includes the following information:
-
Queries from the user.
-
The complete message sent to the configured Large Language Model (LLM) provider, which includes system instructions, referenced documentation, and the user question.
-
The complete response from the LLM provider.
Transcripts originate from the cluster and are associated with the cluster. Red Hat can assign specific clusters to specific customer accounts. Transcripts do not contain any information about users.
Feedback collection overview
OpenShift Lightspeed collects feedback from users who engage with the feedback feature in the virtual assistant interface. If a user submits feedback, the feedback score (thumbs up or down), text feedback (if entered), the user query, and the LLM provider response are stored and sent to Red Hat on the same schedule as transcript collection. If you are using the filtering and redaction functionality, the filtered or redacted content is sent to Red Hat. Red Hat will not see the original non-redacted content, and the redaction takes place before any content is captured in logs.
Feedback is associated with the cluster from which it originated, and Red Hat can attribute specific clusters to specific customer accounts. Feedback does not contain any information about which user submitted the feedback, and feedback cannot be tied to any individual user.