Key highlights
Enhanced Security and Future-Ready Safeguards
With the Managed Fusion 5.9.9 release, we’ve upgraded Kafka to version 3.7.0, incorporating the latest security updates to strengthen your platform’s resilience. Additionally, we’ve implemented critical updates for Managed Fusion’s Webapps, Templating, and API Gateway services, ensuring robust protection for your data. Looking ahead, we’ve introduced enhancements to streamline and expedite the delivery of future security updates, providing you with a safer Managed Fusion environment.Secure deployments with immutable root file system
Fusion now supports a read-only root file system to safeguard against unauthorized modifications, protecting your deployment against malicious software and other attacks. Most services operate efficiently in this mode, and for components that need write access, a separate writable mount is available. Read-only mode is enabled by default for some Managed Fusion services. See Read-only root file system for a list of services that support it or have it enabled by default. It should only be enabled for services that do not require CRUD access. Contact Lucidworks to customize how read-only root file system access is configured for your Managed Fusion deployment.Bug fixes
- This release improves compatibility between Solr and Managed Fusion’s LWAI Prediction index pipeline stage to prevent errors about incompatible characters in field names.
-
The Managed Fusion API realm can now authenticate when an API key is passed via an
apiKey
parameter.
Previously, the key could only be passed in the header, as in these examples:Now you can also pass the key as a parameter, like this: - The Configurations and ZooKeeper Import/Export APIs are now accessible only to authorized users from within Managed Fusion.
Known issues
- Saving large pipelines during high traffic may trigger service instability.
In some environments, saving large query pipelines while handling high traffic loads can cause the Query service to crash with OOM errors due to thread contention. Managed Fusion 5.9.14 resolves this issue. If you’re impacted and not yet on this version, contact Lucidworks Support for mitigation options.
Deprecations
For full details on deprecations, see Deprecations and Removals. As part of our ongoing initiative to replace our V1 (Classic) connectors with our more secure, flexible, and scalable V2 (Plugin) connectors, the following V1 connectors are deprecated in this release: Learn more about V1 and V2 connectors.FAQHow long will Lucidworks continue to support these connectors?These connectors will remain available for at least 6 months from the release of Managed Fusion 5.9.9 and will be removed in a release after this 6-month period.
Removals
For more information, see Deprecations and 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.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.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.9 (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. |