After upgrading to a new platform version, always ensure that your installed component versions match the versions specified in the release notes. To verify this, navigate to FlowX.AI Designer → Platform Status.
Upgrade overview
FlowX.AI 5.9.7 is a maintenance release for the 5.9.x LTS line. The upgrade from 5.9.6 adds no Kafka topics and no database migrations. If you scrape the services with the Prometheus Operator, one Helm value for relabeling is renamed. Review Configuration changes and the 5.9.7 upgrade notes before you deploy.Upgrade Path
5.9.6 → 5.9.7: Direct upgrade. No manual data migration is required. Run it as a rolling upgrade without downtime, see Upgrade within an LTS family.5.9.7 → 6.0.0: See Migrating from v5.9.x to v6.0.0.Self-hosted customers still on the 5.1.x LTS upgrade directly to the 5.9.x line. See Migrating from 5.1 LTS.
Upgrading from 5.9.5 or earlier directly? Review the 5.9.6 deployment guidelines first, then the earlier pages they point to.
Component versions
Core components
* The reporting plugin is an optional add-on and is versioned independently of the platform, so its numbering does not follow the other components. It moved from the
0.2.x scheme to 10.x after 5.9.0. Pin the version listed for your release.
Embedded components
- SpiceDB 1.56.2, deployed and upgraded by the SpiceDB operator 1.27.1.
- Qdrant (vector database): bundled in the
flowx-aiHelm chart; its version is managed by the chart and not pinned here. See the Qdrant setup guide for deployment and configuration.
Renderers
AI components
FlowX.AI groups AI services into four tiers by deployment role. AI Base components are the foundation; AI Runtime and AI Dev Time components both require Base to be installed first; AI Extensions are optional add-ons layered on top.AI Base components
AI Runtime components
AI Dev Time components
AI Extensions
For the plugins matrix, refer to the 5.9.0 deployment guidelines.
Kafka topics
5.9.7 adds, removes, or renames no Kafka topics. For the full multi-release topic matrix, see the 5.9.0 deployment guidelines.Deployment notes
Standard deployment
This maintenance release follows standard FlowX.AI deployment procedures:- Review Configuration changes. If you set
metrics.serviceMonitor.relabellingsin your Helm values, rename it before you deploy. If you deploy with Argo CD or run several FlowX releases on one cluster, read SpiceDB CRD first. - Update container images to the 5.9.7 versions listed in the tables above.
- Deploy services using your standard deployment process.
- Verify deployment via FlowX.AI Designer → Platform Status.
Configuration changes
Prometheus ServiceMonitor
TheServiceMonitor that the FlowX Helm charts create for each service now selects the service’s management Service and scrapes /manage/actuator/prometheus on the mngt port. Before this release, the monitors of most services matched no Service, so Prometheus collected no metrics from them.
The relabeling values now use the names of the Prometheus Operator ServiceMonitor fields:
The charts no longer read
metrics.serviceMonitor.relabellings. If you set it, move its rules to metrics.serviceMonitor.metricRelabelings, where the flowx-ai chart applied them before, or to metrics.serviceMonitor.relabelings for rules that act on target labels.
Audit index retention
The Audit service can now delete old audit data and roll over by shard size. Both settings are off by default, so the Audit service doesn’t delete data unless you set a retention period.API description endpoints
The services no longer serve the Swagger UI or the OpenAPI description./swagger-ui.html, /swagger-ui/**, and /v3/api-docs/** are no longer in the default SECURITY_PUBLICPATHS list. If you overrode SECURITY_PUBLICPATHS, you can remove these paths from your value.
SpiceDB CRD
Thespicedbclusters.authzed.com CRD now ships in its own spicedb-operator-crds subchart of the flowx and flowx-ai Helm charts, instead of the spicedb-operator subchart, behind a new value:
argocd.argoproj.io/sync-options: Prune=false,Delete=false annotation, so Argo CD doesn’t prune it or delete it with the Application.
Setting the value to
false never removes an existing CRD. Upgrading the CRD is still a manual kubectl apply of the new CRD when the operator is upgraded.
Confirm any required configuration changes against the setup guides before upgrading.
Third-party supported component versions
Within each version line listed below, versions that have reached upstream end of life are not supported, even though their major/minor is listed.
(*) Required only if using indexing via Kafka. Multiple sink connector implementations also work, as long as they are compatible with both the deployed Kafka and Elasticsearch version.
The table lists version lines, not individual versions. A version is supported for as long as its vendor still supports it, so check the version you plan to deploy against that vendor’s lifecycle page before committing to it. When a version reaches upstream end of life it is no longer supported; upgrade that component to keep your deployment on a supported configuration. Versions can also be added during the family’s lifetime as FlowX validates them.
For previous FlowX.AI releases, please refer to the Release Notes overview.

