Chapter 1. OpenShift Lightspeed release notes


The release notes highlight what is new and what has changed with each Red Hat OpenShift Lightspeed release.

Important

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 2.0.1

Red Hat OpenShift Lightspeed 2.0.1 adds access to mutating and write tools through the OpenShift Container Platform Model Context Protocol (MCP) server, resolves tool-result inspection regressions with clearer insight into why a result is rejected, and includes CVE fixes across component repositories. This release also improves the autonomous agents log viewing experience in the OpenShift Container Platform web console and helps ensure continued support and stability for clusters running OpenShift Container Platform 4.16 and later.

Note

The latest Offline Knowledge Portal (OKP) image that includes OpenShift Container Platform 5 documentation is not available in Red Hat OpenShift Lightspeed 2.0.1. This image is planned for a future release.

1.1.1. Enhancements

Red Hat OpenShift Lightspeed 2.0.1 adds access to mutating and write tools through the OpenShift Container Platform MCP server and adds log download and raw log viewing controls to the OpenShift Lightspeed autonomous agents log viewer.

Red Hat OpenShift Lightspeed 2.0.1 includes the following enhancements:

  • With this update, Red Hat OpenShift Lightspeed can access mutating and write tools that are exposed through the OpenShift Container Platform Model Context Protocol (MCP) server. This capability lets autonomous agents use tools that change cluster state, in addition to read-only tools. Before this update, the built-in OpenShift Container Platform MCP server did not expose tools that are marked as destructive. These tools are available when introspection is enabled, and you can control them by using the disable_destructive flag. Executing a tool remains subject to the requesting user’s Kubernetes permissions and configured controls.
  • With this update, the per-stage log viewer for AgenticRun workflows in the OpenShift Container Platform web console provides a Download action to save logs as a file and a View raw logs action to open the unformatted logs in a new browser tab. These controls appear on the run detail page for the analysis, execution, and verification stages, and they match the log viewing experience in the Pod Logs view.

1.1.2. Fixed issues

Red Hat OpenShift Lightspeed 2.0.1 resolves tool-result inspection regressions and provides better insight into why a tool result is rejected.

Red Hat OpenShift Lightspeed 2.0.1 fixes the following issues:

  • Before this update, tool-result inspection could fail to classify results when using reasoning-capable models or Anthropic models hosted on Vertex AI. With this update, these classifier paths are corrected. If inspection cannot be completed, Red Hat OpenShift Lightspeed reports that condition separately from a tool result that fails safety inspection.

1.1.3. Fixed security issues

Red Hat OpenShift Lightspeed 2.0.1 includes CVE fixes across component repositories. You can view the security issues fixed in Red Hat OpenShift Lightspeed at Red Hat Security Updates.

1.2. OpenShift Lightspeed version 2.0

Red Hat OpenShift Lightspeed 2.0 provides new features, security fixes, and stability improvements. This release helps ensure continued support and stability for clusters running OpenShift Container Platform 4.16 and later.

1.2.1. Enhancements

Red Hat OpenShift Lightspeed 2.0 introduces autonomous troubleshooting as a Technology Preview feature, along with expanded large language model (LLM) provider support, new observability and compliance capabilities, and greater transparency into how OpenShift Lightspeed handles your data.

Red Hat OpenShift Lightspeed 2.0 includes the following enhancements:

Note

The OpenShift Lightspeed autonomous agents features require OpenShift Container Platform 5.0. These features include autonomous troubleshooting and the configuration of autonomous agents by using the LLMProvider, Agent, and ApprovalPolicy custom resources (CRs). The OpenShift Lightspeed intelligent assistant continues to support OpenShift Container Platform 4.16 and later.

  • With this update, OpenShift Lightspeed introduces OpenShift Lightspeed autonomous agents for autonomous troubleshooting (Technology Preview). An AI-powered agent diagnoses cluster alerts and proposes one-click remediations in the OpenShift Container Platform web console by running multi-step, tool-calling workflows against your cluster. A human-in-the-loop approval step governs every remediation action.
  • With this update, you configure OpenShift Lightspeed autonomous agents (Technology Preview) by using a chain of cluster-scoped custom resources (CRs), including LLMProvider, Agent, and ApprovalPolicy, in the agentic.openshift.io/v1alpha1 API group. OpenShift Lightspeed autonomous agents supports multiple LLM provider backends, including Anthropic, OpenAI, Azure OpenAI, Amazon Web Services (AWS) Bedrock, Google Vertex AI, and Anthropic-compatible vLLM servers.
  • With this update, the OpenShift Lightspeed Operator 2.0 bundles both the OpenShift Lightspeed intelligent assistant and OpenShift Lightspeed autonomous agents into a single Operator installation.
  • With this update, you can use OpenShift Lightspeed to generate interactive Red Hat build of Perses charts from natural language queries and save them directly to your dashboards, without manually writing PromQL queries.

With this update, OpenShift Lightspeed adds audit logging and tracing for AI-assisted and agentic workflows. These records support reconstruction of key AI actions, including user/request correlation for the intelligent assistant, agentic proposals, approval identity, and executed actions.

  • With this update, the documentation describes the OpenShift Lightspeed trust boundary and data flow architecture, the security controls that OpenShift Lightspeed applies by default in each deployment mode, and the prompt injection safeguards, including active tool-result safety inspection that detects and blocks injection attempts embedded in tool output.
  • With this update, a glossary of artificial intelligence (AI) terms and Red Hat OpenShift Lightspeed product terms is available to help you understand the terminology used throughout the documentation.
Important

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.2.2. Fixed issues

Red Hat OpenShift Lightspeed 2.0 resolves a known issue from version 1.1.5 where tool-result inspection could fail at the tool call step for certain models.

Red Hat OpenShift Lightspeed 2.0 fixes the following issues:

  • Before this update, tool-result inspection failed during the tool call step for certain models across supported providers, which prevented the tool call from completing successfully. With this update, tool-result inspection completes reliably during the tool call step, and tool calls finish successfully.
  • Before this update, an issue with the temperature parameter for OpenAI models caused unexpected model responses. With this update, the temperature parameter is processed correctly for OpenAI providers.
  • Before this update, an incorrect build path for the Bring Your Own (BYO) Knowledge tool caused builds to fail. With this update, the BYO Knowledge build path aligns with the documentation, and builds complete successfully.

1.2.3. Fixed security issues

You can view the security issues fixed in Red Hat OpenShift Lightspeed at Red Hat Security Updates.

1.2.4. Known issues

Review the following known issues for Red Hat OpenShift Lightspeed 2.0.

  • Tool classifier can fail a tool result as malicious with larger contexts

    The tool classifier has been observed to incorrectly fail a tool result as malicious when processing larger contexts.

    Workaround: Turn off tool inspection in your Red Hat OpenShift Lightspeed configuration custom resource (CR).

1.3. OpenShift Lightspeed version 1.1.5

Red Hat OpenShift Lightspeed 1.1.5 addresses security vulnerabilities, fixes software bugs, and improves stability. This release helps ensure continued support and stability for clusters running OpenShift Container Platform 4.16 and later.

1.3.1. Enhancements

Red Hat OpenShift Lightspeed 1.1.5 remediates the get_alerts tool functionality by updating the Alertmanager port used by the OpenShift Container Platform Model Context Protocol (MCP) server.

Red Hat OpenShift Lightspeed 1.1.5 includes the following enhancements:

  • With this update, the OpenShift Container Platform Model Context Protocol (MCP) server connects to Alertmanager on the correct port, 9094, to align with the OpenShift Container Platform monitoring stack. This ensures that questions that require the get_alerts tool work as expected.

1.3.2. Fixed security issues

You can view the security issues fixed in Red Hat OpenShift Lightspeed at Red Hat Security Updates.

1.3.3. Known issues

Red Hat OpenShift Lightspeed 1.1.5 contains a known issue where tool-result inspection can fail at the tool call step for certain models.

  • Tool-result inspection can fail at the tool call step for certain models

    Tool-result inspection might fail at the tool call step for certain models across the supported providers. When this issue occurs, the tool call does not complete successfully.

    Workaround: Disable the tool-result inspection flag in your Red Hat OpenShift Lightspeed configuration custom resource (CR).

1.4. OpenShift Lightspeed version 1.1.4

Red Hat OpenShift Lightspeed 1.1.4 addresses security vulnerabilities, adds enhancements, and improves stability. This release helps ensure continued support and stability for clusters running OpenShift Container Platform 4.16 and later.

1.4.1. Enhancements

Red Hat OpenShift Lightspeed 1.1.4 updates the Red Hat Offline Knowledge Portal (RHOKP) that provides OpenShift Container Platform documentation for retrieval-augmented generation (RAG), and updates how the OpenShift Container Platform Model Context Protocol (MCP) server is delivered.

Red Hat OpenShift Lightspeed 1.1.4 includes the following enhancements:

  • With this update, OpenShift Lightspeed includes Red Hat Offline Knowledge Portal (RHOKP) version 1.2.12, which refreshes the OpenShift Container Platform product documentation in the RAG knowledge base and expands coverage to the most recent seven OpenShift Container Platform versions. For more information, see RHBA-2026:62194.
  • With this update, OpenShift Lightspeed uses the image published by the OpenShift MCP team to deliver the OpenShift Container Platform Model Context Protocol (MCP) server. As a result, you receive the latest MCP server updates through Red Hat OpenShift Lightspeed.
  • With this update, OpenShift Lightspeed includes an OpenTelemetry (OTel) collector for logging. You can use it to collect and forward Red Hat OpenShift Lightspeed logs.

1.4.2. Fixed security issues

You can view the security issues fixed in Red Hat OpenShift Lightspeed at Red Hat Security Updates.

1.4.3. Known issues

Red Hat OpenShift Lightspeed 1.1.4 contains a known issue where questions that require the get_alerts tool time out.

  • Questions that require the get_alerts tool time out

    Any question that requires the get_alerts tool times out and does not return a response. This issue does not affect test or evaluation workflows.

    Workaround: There is currently no workaround for this issue.

1.5. OpenShift Lightspeed version 1.1.3

Red Hat OpenShift Lightspeed 1.1.3 addresses security vulnerabilities and improves stability. This release helps ensure continued support and stability for clusters running OpenShift Container Platform 4.16 and later.

1.5.1. Fixed security issues

You can view the security issues fixed in Red Hat OpenShift Lightspeed at Red Hat Security Updates.

1.5.2. Known issues

Red Hat OpenShift Lightspeed 1.1.3 contains known issues regarding incorrect documentation version references in the Red Hat Offline Knowledge Portal (RHOKP) RAG source and missing branding logos in the console interface.

  • Incorrect documentation version referenced by the RHOKP RAG source

    When you use the RHOKP RAG source on OpenShift Container Platform 4.16 and 4.17 clusters, OpenShift Lightspeed references OpenShift Container Platform 4.18 documentation instead of the matching cluster version. As a result, responses generated from product documentation might reflect behavior or features that do not apply to your cluster version.

    Workaround: There is currently no workaround for this issue.

  • Missing branding logos in the OpenShift Lightspeed console interface

    Branding logos and visual identity markers do not render in the assistant panel when you open OpenShift Lightspeed in the OpenShift Container Platform web console. Only the panel text and standard console icons remain visible. This is a visual issue and does not affect assistant capabilities, prompts, or navigation.

    Workaround: There is currently no workaround required, as core functionality is unaffected.

1.6. OpenShift Lightspeed version 1.1.2

Red Hat OpenShift Lightspeed 1.1.2 addresses security vulnerabilities, fixes software bugs, and improves stability. This release helps ensure continued support and stability for clusters running OpenShift Container Platform 4.16 and later.

1.6.1. Enhancements

Red Hat OpenShift Lightspeed 1.1.2 introduces support for the Amazon Web Services (AWS) Bedrock model provider and replaces the custom RAG implementation with the Offline Knowledge Portal (OKP) for OpenShift Container Platform documentation retrieval. This release also adds support for OpenShift Container Platform 4.22 and ROSA-aware documentation retrieval.

Red Hat OpenShift Lightspeed 1.1.2 includes the following enhancements:

  • With this update, cluster administrators can configure AWS Bedrock as a large language model (LLM) provider in the OLSConfig custom resource (CR).
  • With this update, OpenShift Lightspeed replaces the previous custom OLS RAG implementation with OKP for serving OpenShift Container Platform product documentation. The Operator deploys a Red Hat Offline Knowledge Portal (RHOKP) sidecar on the app-server pod and configures Solr hybrid retrieval for the cluster’s OpenShift Container Platform version.

    Cluster administrators can tune RHOKP sidecar CPU, memory, and ephemeral storage (disk) by using spec.ols.deployment.rhokp on the OLSConfig custom resource (CR). RHOKP requires substantial disk space for Solr data; the Operator’s recommended default request is 75 GiB ephemeral storage, along with 2 CPU and 2 GiB memory.

    The initial setup of the OKP RAG system might take some time while the documentation corpus is indexed. During this period, OpenShift Lightspeed might not return documentation-grounded answers.

  • With this update, OpenShift Lightspeed adds support for OpenShift Container Platform 4.22.
  • With this update, OpenShift Lightspeed automatically detects Red Hat OpenShift Service on AWS (ROSA) clusters and includes ROSA-specific documentation alongside OpenShift Container Platform documentation. On OpenShift clusters, behavior remains unchanged.

1.6.2. Known issues

Red Hat OpenShift Lightspeed 1.1.2 contains a known issue where the initial installation and pod startup for the OKP RAG system takes additional time to complete indexing when upgrading from version 1.1.1 to 1.1.2.

The following issues are identified with Red Hat OpenShift Lightspeed 1.1.2:

  • Initial installation delay for the OKP RAG system

    When you upgrade from version 1.1.1 to 1.1.2, the initial installation and pod startup for the OKP RAG system takes additional time to complete indexing. Standard restarts take less time.

    During this initial setup, OpenShift Lightspeed is temporarily unavailable. You must wait for the indexing process to finish before expecting full RAG functionality.

    Workaround: None.

1.7. OpenShift Lightspeed version 1.1.1

Red Hat OpenShift Lightspeed 1.1.1 addresses security vulnerabilities, fixes software bugs, and improves stability. This release helps ensure continued support and stability for clusters running OpenShift Container Platform 4.16 and later.

1.7.1. Fixed security issues

You can view the security issues fixed in Red Hat OpenShift Lightspeed at Red Hat Security Updates.

1.8. OpenShift Lightspeed version 1.1

Red Hat OpenShift Lightspeed 1.1 provides maintenance updates, security fixes, and feature enhancements. This release helps ensure continued support and stability for clusters running OpenShift Container Platform 4.16 and later.

1.8.1. Enhancements

Red Hat OpenShift Lightspeed 1.1 introduces security enhancements for secret handling, updated component management, and support for modern AI software development kits.

Red Hat OpenShift Lightspeed 1.1 includes the following enhancements:

  • Previously, copying a response from OpenShift Lightspeed only included raw markdown text. With this update, copying a response from OpenShift Lightspeed to the clipboard preserves formatting when you paste it into applications that support rich text, such as Google Docs.
  • With this update, the introspectionEnabled field in the OLSConfig custom resource (CR) is true by default. You do not have to specify this field to use the Kubernetes Model Context Protocol (MCP) server. To disable the Kubernetes MCP server, you must set this field to false.
  • With this update, the Kubernetes MCP server supports both read and write operations. Because human-in-the-loop (HITL) support is enabled by default, you must approve any non-read operation, such as an update or delete, in the user interface before OpenShift Lightspeed executes the action. This behavior is controlled by the toolsApprovalConfig.approvalType field in the OLSConfig custom resource (CR), which defaults to tool_annotations.
  • With this update, you can expand code blocks to view more content and collapse them to return to their original size.
  • With this update, OpenShift Lightspeed supports only the strong ciphers and Transport Layer Security (TLS) profiles recommended by Red Hat Product Security. This enhancement prevents the use of weak signature algorithms to ensure that your cluster remains protected and compliant with security standards.
  • With this update, you can attach Prometheus alerting rules and Alertmanager silences to a prompt directly from their details pages.
  • With this update, OpenShift Lightspeed supports Google Vertex AI as an LLM provider. You can configure Google-native models, such as Gemini, by using the google_vertex provider type. You can also configure Anthropic models, such as Claude hosted on Vertex AI, by using the google_vertex_anthropic provider type. Both provider types authenticate by using a Google Cloud Platform (GCP) service account JSON key stored within a Kubernetes Secret.

1.9. OpenShift Lightspeed version 1.0

Red Hat OpenShift Lightspeed version 1.0 provides an AI-driven intelligent assistant that helps users troubleshoot and manage OpenShift clusters. This release introduces support for OpenShift Container Platform 4.15 and later.

1.9.1. Enhancements

Red Hat OpenShift Lightspeed 1.0 introduces general availability support for OpenShift Container Platform 4.15 and later. This release includes new AI-driven cluster interaction capabilities, security updates, and several Technology Preview features.

The following enhancements are made with Red Hat OpenShift Lightspeed 1.0:

  • Cluster interaction
  • PostgreSQL persistence
  • Token quota
Important

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.9.2. Known issues

Red Hat OpenShift Lightspeed 1.0 includes known issues related to web console interface visibility, quota configuration updates, and database connectivity. Use the provided workarounds to resolve these issues and maintain service availability in your OpenShift cluster.

The following issues are identified with Red Hat OpenShift Lightspeed 1.0:

  • 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:

    • 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 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.

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