Managed Fusion 5.9.14 is a maintenance release that introduces official support for Kubernetes 1.33, introduces the new Local Chunker index stage for Ray-hosted model support, and adds enhanced monitoring and asynchronous processing for pipelines. It also includes structured JSON logging for easier observability and log management, along with a wide range of internal security and hardening updates that strengthen platform reliability and compliance.
For supported Kubernetes versions and key component versions, see Platform support and component versions.

​
Key highlights

​
Support for Kubernetes 1.33

Managed Fusion now runs on Kubernetes 1.33. This update keeps your deployment environment aligned with the latest Kubernetes platform standards. Why this matters:
  • Stronger security: Your cluster benefits from the most recent Kubernetes security fixes and hardening improvements.
  • Improved compatibility: Kubernetes 1.33 ensures smoother integration with third-party tools and services that expect newer versions of the platform.
  • Operational consistency: The upgrade reduces friction during promotions, scaling events, and rolling updates, helping your teams work more efficiently.
This version update helps ensure that your environment remains secure, reliable, and easy to manage.

​
New Local Chunker index stage

Managed Fusion 5.9.14 adds a new Local Chunker index pipeline stage that performs document chunking using models hosted in your own Ray infrastructure as an alternative to SaaS-based Lucidworks AI. This makes it easier to deploy RAG pipelines in fully self-hosted environments. This stage gives you control over chunk processing and storage, with the option to include or exclude chunk text depending on your deployment preferences. By default, it uses the vector context variable as input, aligning with the output of Ray-hosted models.

​
Asynchronous processing for LWAI Vectorize Query and LWAI Prediction pipeline stages

To help reduce query latency and improve overall performance, the LWAI Vectorize Query and LWAI Prediction stages now support asynchronous execution. This enhancement allows more efficient parallel processing in pipelines that use multiple AI-powered stages. As with other async-enabled stages, you can aggregate results using the Merge Async Results stage stage.

​
Improved visibility for Solr ingestion errors

Managed Fusion 5.9.14 enhances logging for Solr indexing. These improvements make it easier to identify and address problematic documents without losing valid ones:
  • The system logs detailed information about each document that fails to index, including the cause of the error.
  • Logs use a structured, machine-readable format, making them easier to parse and monitor.
  • Indexing continues for valid documents even when some fail, preventing unnecessary data loss.
These changes help you troubleshoot ingestion issues faster, trace failures to specific documents, and keep indexing pipelines running smoothly in Managed Fusion environments.

​
Security improvements

Managed Fusion 5.9.14 includes a broad set of internal security fixes and hardening updates. These updates improve the overall security posture of the platform by addressing potential vulnerabilities and ensuring better alignment with secure development best practices. This ongoing work helps protect your deployments from evolving threats and ensures Managed Fusion continues to meet enterprise-grade security standards.

​
Bug fixes

  • Fixed an issue where certain datasource jobs could not be stopped.
Managed Fusion 5.9.14 resolves this issue and restores proper job control behavior.
  • Fixed excessive debug logging in Spark driver pods.
Managed Fusion 5.9.14 reduces logging verbosity by default and improves configurability of log level settings for Spark drivers.
  • Fixed pipeline errors in Commerce Studio caused by empty or invalid collection names.
Managed Fusion 5.9.14 resolves this issue by correcting the thread handling logic, validating collection name inputs, and raising logging levels to warn when invalid configurations are detected, helping you troubleshoot more effectively and avoid unnecessary pipeline failures.
  • Fixed an issue where Spark jobs would disappear from Managed Fusion after pod deletion.
Managed Fusion 5.9.14 ensures Spark jobs remain visible and manageable even after pod restarts.
  • Improved stability when saving large pipelines during promotions under load.
Managed Fusion now prevents out-of-memory crashes that previously occurred when saving large query pipelines during high traffic, such as during staging promotions.
  • Fixed job and datasource errors when Managed Fusion collections pointed to remapped Solr collections.
Previously, jobs and V2 datasources failed with “Collection not found” errors when a Managed Fusion collection pointed to a Solr collection with a different name. Managed Fusion 5.9.14 removes this restriction, allowing jobs and datasources to work with valid Managed Fusion collections regardless of Solr collection naming, restoring expected behavior and improving compatibility with remapped environments.
  • Fixed incorrect “down” status in job-config service for Managed Fusion
In some cases, the job-config service appeared as “down” in the Managed Fusion UI, despite running correctly. This status reporting issue is fixed in Managed Fusion 5.9.14, ensuring accurate visibility into service health.

​
Known issues

  • In some asynchronous pipeline stages, the “Asynchronous Execution Config” checkbox is misaligned such that the checkbox is not directly clickable. To work around this issue, click on the checkbox title, “Asynchronous Execution Config”.

​
Removals

​
Bitnami removal

By August 28, 2025, Fusion’s Helm chart will reference internally built open-source images instead of Bitnami images due to changes in how they host images. This release includes an updated Helm chart with new image references.

​
Platform Support and Component Versions

​
Kubernetes platform support

Lucidworks has tested and validated support for the following Kubernetes platform and versions:
  • Google Kubernetes Engine (GKE): 1.29, 1.30, 1.31, 1.32, 1.33
For more information on Kubernetes version support, see the Kubernetes support policy.

​
Component versions

The following table details the versions of key components that may be critical to deployments and upgrades.
ComponentVersion
Solrfusion-solr 5.9.14 (based on Solr 9.6.1)
ZooKeeper3.9.1
Spark3.4.1
Ingress ControllersNginx, Ambassador (Envoy), GKE Ingress Controller
Rayray[serve] 2.46.0
More information about support dates can be found at Lucidworks Fusion Product Lifecycle.