oci://registry.falkordb.cloud/falkordb/falkordb-enterprise.
See Compatibility matrix for the subchart versions that ship with
each release, and Upgrade FalkorDB Enterprise for the upgrade procedure.
Added
- Scheduling policy support for deployments. Node selectors and tolerations can be set per component for FalkorDB, Sentinel, and shards, from the deployment wizard and from the Admin Server API.
- Administrators can reset a user’s password.
Changed
- The
falkordb-browsersubchart moves from 2.0.9 to 2.4.0. It now readsglobal.imageRegistry, so the umbrella chart no longer overridesfalkordb-browser.image.repository. Mirrored registries needfalkordb-browser:v2.4.0before upgrading. - The
csi-s3subchart moves from 0.43.4 to 0.43.7.
Fixed
csi-s3andcsi-driver-nfsimages updated to clear reported vulnerabilities.
Breaking changes
- First-party images and the Helm chart are published to
registry.falkordb.cloudinstead ofghcr.io. Existing image pull secrets, mirror configurations, and any pinnedghcr.ioimage references have to be updated. See Migrate from 0.3 to 0.4. - The chart no longer injects a default image registry through the installer. The
registry comes from the chart’s own
global.imageRegistryvalue, so a registry supplied through-f values.yamlis no longer outranked.
Added
- Publish summary scripts for the enterprise database image.
Fixed
- Helm upgrades read the release revision correctly and wait for addon definitions to reconcile before continuing.
- Admin UI: max uptime renders as a readable duration, memory metrics agree between tabs, and small non-zero CPU and memory percentages are no longer rounded away.
Added
- External DNS support, including per-pod DNS records and configuration from the standalone and sharded deployment wizards.
- A confirmation dialog for starting and stopping a deployment.
Changed
- The FalkorDB addon subchart moves to 1.7.1.
- User-facing terminology changed from “cluster” to “deployment”.
Fixed
- Deployments stuck in
Pendingcan be updated, so a failed create no longer strands them.