Chapter 1. Evaluate OpenShift Lightspeed capabilities


Red Hat OpenShift Lightspeed is a generative AI service that helps developers and administrators solve problems by providing context-aware recommendations for OpenShift Container Platform.

1.1. OpenShift Lightspeed overview

Use Red Hat OpenShift Lightspeed to fix and manage your OpenShift clusters. You can operate the virtual assistant by using plain English right inside the OpenShift web console.

1.1.1. Supported interfaces

OpenShift Lightspeed categorizes programmatic and user interactions by their stability level so that you can determine the support and reliability of specific features. Use these categories to identify which APIs and interfaces are stable for production or intended for testing.

OpenShift Lightspeed provides the following interfaces:

  • REST API: The OpenShift Lightspeed REST API, hosted at the /v1/ path, is the stable and supported interface for programmatic interactions.
  • Gradio UI and internal endpoints: The Gradio UI (/ui) and all internal endpoints are for development and debugging only. These interfaces are unstable. You must not use these interfaces for programmatic purposes.

Red Hat OpenShift Lightspeed answers your questions by using information from official OpenShift Container Platform documentation. On Red Hat OpenShift Service on AWS (ROSA) clusters, OpenShift Lightspeed automatically detects the ROSA deployment type and includes ROSA-specific documentation alongside OpenShift Container Platform documentation.

1.1.2.1. Product exceptions

The OpenShift Container Platform documentation does not cover every Red Hat product. Because of this, OpenShift Lightspeed uses your large language model (LLM) to create answers for these products:

  • Builds for Red Hat OpenShift
  • Red Hat Advanced Cluster Security for Kubernetes
  • Red Hat Advanced Cluster Management for Kubernetes
  • Red Hat CodeReady Workspaces
  • Red Hat OpenShift GitOps
  • Red Hat OpenShift Pipelines
  • Red Hat OpenShift Serverless
  • Red Hat OpenShift Service Mesh 3.x
  • Red Hat Quay

1.2. OpenShift requirements

Hardware and software requirements for OpenShift Lightspeed, including supported OpenShift Container Platform versions and CPU architectures.

OpenShift Container Platform clusters enable telemetry by default.

  • When telemetry is on, OpenShift Lightspeed sends your chats and feedback to Red Hat.
  • When telemetry is off, OpenShift Lightspeed does not send this data.
  • To stop OpenShift Lightspeed from sending your chats and feedback, you must disable telemetry for the whole cluster.

1.2.1. Cluster resource requirements

Ensure that OpenShift Lightspeed has enough CPU, memory, and storage allocations to support Service performance and cluster stability without impacting other cluster workloads.

ComponentMinimum CPU (Cores)Minimum MemoryMaximum Memory

Application server

0.5

1 GB

4 Gi

PostgreSQL database

0.3

300 Mi

2 Gi

OpenShift Container Platform web console

0.1

50 Mi

100 Mi

OpenShift Lightspeed operator

0.1

64 Mi

256 Mi

1.3. Large language model (LLM) requirements

OpenShift Lightspeed supports Software as a Service (SaaS) and self-hosted large language model (LLM) providers that meet defined authentication requirements.

The LLM is a type of machine learning model that interprets and generates human-like language. When you use the LLM with a virtual assistant, the LLM can accurately interpret questions and offers helpful answers in a conversational manner. The OpenShift Lightspeed Service must have access to the LLM provider.

The Service does not provide the LLM for you, so you must configure the LLM before installing the OpenShift Lightspeed Operator.

Note

Red Hat does not provide support for any specific models or make suggestions or support statements pertaining to models.

The OpenShift Lightspeed Service can rely on the following SaaS LLM providers:

  • OpenAI
  • Microsoft Azure OpenAI
  • IBM watsonx

If you want to self-host a model, you can use Red Hat OpenShift AI or Red Hat Enterprise Linux AI as your model provider.

1.3.1. IBM watsonx

To use IBM watsonx with Red Hat OpenShift Lightspeed, you need an account with IBM Cloud watsonx. For more information, see the Documentation for IBM watsonx as a Service.

1.3.2. Open AI

To use OpenAI with Red Hat OpenShift Lightspeed, you need access to the OpenAI API platform. For more information, see the OpenAI developer platform documentation.

1.3.3. Microsoft Azure OpenAI

To use Microsoft Azure with Red Hat OpenShift Lightspeed, you need access to Microsoft Azure OpenAI. For more information, see the Azure OpenAI documentation.

1.3.4. Red Hat Enterprise Linux AI

Red Hat Enterprise Linux AI is OpenAI API-compatible, and you configure Red Hat Enterprise Linux AI in a similar manner as the OpenAI provider.

You can configure Red Hat Enterprise Linux AI as the LLM provider.

Because the Red Hat Enterprise Linux is in a different environment than the OpenShift Lightspeed deployment, the model deployment must allow access by using a secure connection. For more information, see Optional: Allowing access to a model from a secure endpoint.

OpenShift Lightspeed version 1.0 and later supports vLLM Server version 0.8.4 and later. When self-hosting the LLM with Red Hat Enterprise Linux AI, you can use vLLM Server as the inference engine.

1.3.5. Red Hat OpenShift AI

Red Hat OpenShift AI is OpenAI API-compatible, and you configure Red Hat OpenShift AI largely the same as the OpenAI provider.

You must deploy the LLM on the Red Hat OpenShift AI single-model serving platform that uses the virtual large language model (vLLM) runtime. If the model deployment runs in a different OpenShift environment than the OpenShift Lightspeed deployment, include a route to expose the model deployment outside the cluster. For more information, see About the single-model serving platform.

OpenShift Lightspeed version 1.0 and later supports vLLM Server version 0.8.4 and later. When self-hosting the LLM with Red Hat OpenShift AI, you can use vLLM Server as the inference engine.

1.3.6. Amazon Web Services Bedrock requirements

To use Amazon Web Services Bedrock with OpenShift Lightspeed, you must have an AWS account with authorized access to your chosen models. OpenShift Lightspeed supports establishing a connection to AWS Bedrock through either a bearer token, such as an endpoint managed by a Bedrock Mantle gateway, or standard AWS Identity and Access Management (IAM) security credentials.

Red Hat OpenShift Lightspeed supports Federal Information Processing Standards (FIPS). You can run Red Hat OpenShift Lightspeed on OpenShift clusters that use FIPS mode.

FIPS is a set of publicly announced standards developed by the National Institute of Standards and Technology (NIST), a part of the U.S. Department of Commerce. The primary purpose of FIPS is to ensure the security and interoperability of computer systems used by U.S. federal government agencies and their associated contractors.

Important

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 (NIST). 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.5. Supported architecture

OpenShift Lightspeed works with OpenShift Container Platform clusters that use the x86_64 architecture.

OpenShift Lightspeed works in disconnected clusters without full internet access.

In a disconnected cluster, you must mirror the container images you need. For more help, see "Mirroring in disconnected environments" in the OpenShift Container Platform documentation.

Note

When you mirror images in a disconnected cluster, list the OpenShift Lightspeed Operator with the oc mirror command.

1.7. Data flow architecture

OpenShift Lightspeed communicates directly with your configured large language model (LLM) provider endpoint. No Red Hat-managed cloud services or proxies are involved in the data path between OpenShift Lightspeed and the LLM provider during active chat interactions.

When you submit a prompt, the OpenShift Lightspeed Service pod on your local cluster sends the request directly to your configured LLM provider endpoint. Supporter providers include Azure AI Foundry, OpenAI, and self-hosted models served by OpenShift Container Platform AI. The LLM provider returns its response directly to the OpenShift Lightspeed Service pod. Red Hat infrastructure does not process, route, or store any prompt or response data during this exchange.

Separately, if telemetry is enabled, OpenShift Lightspeed sends conversation data to Red Hat by using the Red Hat Insights system. This telemetry transmission is independent of the prompt and response data flow and can be disabled.

1.8. How your data is used and protected

OpenShift Lightspeed adds cluster and environment details to your messages. Then, it sends this data directly from the OpenShift Lightspeed Service pod on your cluster to the configured large language model (LLM) provider endpoint. No Red Hat-managed cloud services are involved in this data exchange.

OpenShift Lightspeed has limited ability to filter or hide the data you send to the LLM. Do not enter any information into the interface that you want to keep private from the LLM.

When you send transcripts or feedback to Red Hat, you agree that Red Hat can use the data to improve our Service. The transcript recording data uses the Red Hat Insights system. It follows the same security rules and access limits as that system. Telemetry and remote data collection can be completely disabled at your discretion.

To request deletion of your data, open a support ticket with Red Hat.

OpenShift Lightspeed sends your messages and cluster data through a redaction layer. It does this to clean the data before it goes to the LLM.

Do not enter anything into the OpenShift Lightspeed interface that you want to keep private from the LLM.

Conversation data, including user inputs, LLM outputs, tool call details, retrieval-augmented generation (RAG) context, and associated metadata, is only sent to Red Hat if telemetry is enabled. You can disable telemetry to stop all data collection by Red Hat.

The transcript recording data uses the Red Hat Insights system. It follows the same security rules and access limits as that system.

Additional resources

1.10. Remote health monitoring overview

Remote Health Monitoring uses the Telemeter Client and Insights Operator to gather and report cluster information for Red Hat analysis and support.

You can learn how Red Hat collects data in the OpenShift Container Platform documentation. To stop sending chat transcripts or feedback, you must opt out of remote health monitoring. Follow the steps in the "About remote health monitoring" section of the OpenShift Container Platform documentation.

1.10.1. Transcript collection overview

OpenShift Lightspeed sends chat transcripts to Red Hat on a set schedule. The Service uses a redaction layer to filter data before the Service shares or logs it.

By default, OpenShift Lightspeed sends these transcripts every two hours. Red Hat cannot see your original data. OpenShift Lightspeed hides sensitive data before it reaches any logs.

OpenShift Lightspeed saves conversation transcripts for a short time. This includes:

  • 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 come from your cluster and stay linked to it. Red Hat can match these clusters to specific customer accounts. These transcripts do not contain any user data.

1.10.2. Feedback collection overview

OpenShift Lightspeed collects opt-in user feedback from the virtual assistant interface to analyze response accuracy and improve Service quality.

If you submit feedback, Red Hat stores and receives your feedback score, text, and query. Red Hat also receives the large language model (LLM) response on the same schedule as transcripts. When you use the redaction tools, Red Hat receives only the filtered data. Red Hat does not see the original data. OpenShift Lightspeed hides your data before the system logs it.

Your feedback stays associated with the cluster where it began. Red Hat can match these clusters to specific customer accounts. This feedback does not contain any user details, and Red Hat cannot link the feedback to any specific person.

1.11. Data retention and deletion

OpenShift Lightspeed stores interaction data locally in the OpenShift Lightspeed Service pod logs and in your cluster’s configured log aggregation system. Red Hat does not have access to this local data.

If telemetry is enabled, conversation data is sent to Red Hat through the Red Hat Insights system. This data includes user inputs, LLM outputs, tool call details, retrieval-augmented generation (RAG) context, and associated metadata, Red Hat retains data that is collected through telemetry until you submit a formal request for data deletion.

To request deletion of your telemetry data, open a support ticket with Red Hat. Include your cluster identifier and the scope of data that you want to be deleted.

You can disable telemetry at any time to stop all future data collection. Disabling telemetry does not affect data that Red Hat has already collected. To delete previously collected data, you must submit a separate deletion request.

Red Hat does not use customer prompt or response data to train or fine-tune AI models.

When telemetry is enabled, Red Hat uses the collected data exclusively to evaluate and refine internal system prompts and embedding parameters to improve OpenShift Lightspeed Service quality. Any interaction data that is retained for internal evaluation is heavily redacted and anonymized before use.

Red Hat does not train or tune its own AI models using customer interaction data, and does not share customer interaction data with third-party AI model providers for training purposes.

1.13. Additional resources

Red Hat logoGithubRedditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat Documentation

Legal Notice

Theme

© 2026 Red Hat
Back to top