Urgent action required by November 26, 2025A patch is required by November 26, 2025 for all self-hosted Fusion deployments running on Amazon Elastic Kubernetes Service (EKS). Certain Java versions used by Fusion components reach end of life on this date. Failure to apply the patch will result in compatibility issues.
Instructions for applying the patch
Instructions for applying the patch
The following Fusion services require the
Follow these steps to apply the patched images:
cgroupv2 patch:| Service | Affected Fusion versions | Patch tag |
|---|---|---|
insights | 5.9.4 to 5.9.15 | lucidworks/insights:5.9-cgroupv2-patch |
spark-solr-etl | 5.9.4 to 5.9.11 | lucidworks/spark-solr-etl:5.9-cgroupv2-patch |
keytool-utils | 5.9.4 to 5.9.10 | lucidworks/keytool-utils:5.9-cgroupv2-patch |
- Open your Fusion Helm values file. For Fusion Cloud Native deployments, use the values file for your current deployment. For Helm deployments, use the values file you used to create the deployment.
- For each service listed in the following table that applies to your Fusion version, add or update the image configuration:
- Fusion 5.9.4 to 5.9.10
- Fusion 5.9.11
- Fusion 5.9.12 to 5.9.15
- Save the values file.
-
For Fusion Cloud Native deployments, run the
upgrade_fusion.shscript you used for your current deployment. For Helm deployments, run the following command: - Wait for the affected service pods to restart and verify they are using the patched images.
Platform Support and Component Versions
Kubernetes platform support
Lucidworks has tested and validated support for the following Kubernetes platforms and versions:- Google Kubernetes Engine (GKE): 1.28, 1.29, 1.30
- Microsoft Azure Kubernetes Service (AKS): 1.28, 1.29, 1.30
- Amazon Elastic Kubernetes Service (EKS): 1.28, 1.29, 1.30
Component versions
The following table details the versions of key components that may be critical to deployments and upgrades.| Component | Version |
|---|---|
| Solr | fusion-solr 5.9.7 (based on Solr 9.6.1) |
| ZooKeeper | 3.9.1 |
| Spark | 3.2.2 |
| Ingress Controllers | Nginx, Ambassador (Envoy), GKE Ingress Controller Istio not supported. |
New Features
New Lucidworks AI pipeline stages are introduced in this release to enrich your index and search with Generative AI predictions:- The LWAI Prediction index stage allows for asynchronous and synchronous enrichment that add predictions when indexing your data.
See Configure the LWAI Prediction index Stage for more detailed instructions about configuring this stage. - The LWAI Prediction query stage fetches synchronous predictions to add to your query response.
/index-pipelines/{id}/async-enrichment/skip-pending, can be used to clear the queue of outstanding asynchronous prediction index requests if needed.
Removals
Bitnami removal
Fusion 5.9.7 will be re-released with the same functionality but updated image references. In the meantime, Lucidworks will self-host the required images while we work to replace Bitnami images with internally built open-source alternatives. If you are a self-hosted Fusion customer, you must upgrade before August 28 to ensure continued access to container images and prevent deployment issues. You can reinstall your current version of Fusion or upgrade to Fusion 5.9.14, which includes the updated Helm chart and prepares your environment for long-term compatibility. See Prevent image pull failures due to Bitnami deprecation in Fusion 5.9.5 to 5.9.13 for more information on how to prevent image pull failures.Bug fixes
- Fixed an issue where some collections were not displayed in the Collections Manager if the system contained one or more orphaned child collections.
Note that orphaned child collections are not displayed in the Collections Manager by design, but they are discoverable using the API or the Object Manager.