Red Hat Summit Red Hat SummitSupportConsoleDevelopersStart a trialContact

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 1.1
Copy link

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

1.1.1. Enhancements
Copy link

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.2. OpenShift Lightspeed version 1.0
Copy link

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

1.2.1. Enhancements
Copy link

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.2.2. Known issues
Copy link

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

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Legal Notice

Theme

© 2026 Red HatBack to top