FalkorDB Enterprise version compatibility matrix and platform dependencies

Every FalkorDB Enterprise release pins the versions below. Installing a release installs exactly these subcharts, so pick the Enterprise version rather than pinning subcharts individually.

Release channels

stable

The current recommended release, and what a default install gets. Use this unless you have a reason not to.

beta

Early access to new capabilities. Not covered by production support. Published as prerelease versions such as 0.5.0-beta.1, so a default install never picks one up.

lts

Long-term support. Receives fixes for an extended window and is the target for conservative upgrade policies.

Install the latest stable release by omitting --version. To try a beta, pass --channel beta, or name the exact version:

curl -fsSL https://falkordb.github.io/FalkorDB-Enterprise/install.sh | \
  bash -s -- \
    --registry-username '<username>' \
    --registry-password '<token>' \
    --channel beta

Platform components

Enterprise	Channel	KubeBlocks	FalkorDB addon	Browser	SQL migration	Snapshot Controller	KubeBlocks CRDs
`1.0.0-beta.4`	beta	`1.2.0-alpha.1`	`1.7.7`	`2.4.0`	`1.1.6`	`5.0.3`	`v1.2.0-alpha.1`
`1.0.0-beta.3`	beta	`1.2.0-alpha.1`	`1.7.5`	`2.4.0`	`1.1.6`	`5.0.3`	`v1.2.0-alpha.1`
`1.0.0-beta.2`	beta	`1.2.0-alpha.1`	`1.7.5`	`2.4.0`	`1.1.6`	`5.0.3`	`v1.2.0-alpha.1`
`1.0.0-beta.1`	beta	`1.2.0-alpha.1`	`1.7.5`	`2.4.0`	`1.1.6`	`5.0.3`	`v1.2.0-alpha.1`
`0.4.1`	stable	`1.2.0-alpha.1`	`1.7.2`	`2.4.0`	`1.1.6`	`5.0.3`	`v1.2.0-alpha.1`
`0.4.0`	stable	`1.2.0-alpha.1`	`1.7.2`	`2.0.9`	`1.1.6`	`5.0.3`	`v1.2.0-alpha.1`
`0.3.1`	stable	`1.2.0-alpha.1`	`1.7.2`	`2.0.9`	`1.1.6`	`5.0.3`	`v1.2.0-alpha.1`
`0.3.0`	stable	`1.2.0-alpha.1`	`1.7.1`	`2.0.9`	`1.1.2`	`5.0.3`	`v1.2.0-alpha.1`

KubeBlocks CRDs is pinned separately from the KubeBlocks chart. The installer applies CRDs from that reference because later KubeBlocks branches drop fields the FalkorDB addon depends on. Override it with KUBEBLOCKS_CRD_REF only when advised.

Storage drivers

These subcharts are optional and disabled by default. They are pinned per release so an enabled driver stays reproducible.

Enterprise	csi-hostpath-driver	csi-s3	csi-driver-nfs
`1.0.0-beta.4`	`1.14.0`	`0.43.7`	`4.13.1`
`1.0.0-beta.3`	`1.14.0`	`0.43.7`	`4.13.1`
`1.0.0-beta.2`	`1.14.0`	`0.43.7`	`4.13.1`
`1.0.0-beta.1`	`1.14.0`	`0.43.7`	`4.13.1`
`0.4.1`	`1.14.0`	`0.43.7`	`4.13.1`
`0.4.0`	`1.14.0`	`0.43.4`	`4.13.1`
`0.3.1`	`1.14.0`	`0.43.4`	`4.13.1`
`0.3.0`	`1.14.0`	`0.43.4`	`4.13.1`

Tested upgrade paths

Moving a deployment to a newer FalkorDB addon release replaces its definition in one step: nothing an addon release in between would have done runs. So CI upgrades to each release from the newest release of every addon version a supported release shipped, with databases running. The chart upgrade must leave them untouched; each database is then moved to the new addon release and upgraded to the newest FalkorDB version, and must keep its data and topology. Upgrades to 1.0.0-beta.4 are tested from:

From Enterprise	FalkorDB addon before	FalkorDB addon after
`1.0.0-beta.3`	`1.7.5`	`1.7.7`

A release not listed that ships the same addon as a listed one makes the same addon jump. Upgrade a release older than 1.0.0-beta.1 to 1.0.0-beta.1 first, following the migration guide.

Admin components

The Admin Server, Admin UI, and Admin CLI images are tagged with the Enterprise chart version. Chart 0.4.1 runs Admin Server 0.4.1, and so on.

Changelog

What changed in each release.

Upgrade FalkorDB Enterprise

How to move between versions.

Move to a newer addon release

Bring each deployment to the addon release a chart upgrade installed.

​Release channels

stable

beta

lts

​Platform components

​Storage drivers

​Tested upgrade paths

​Admin components

​Related

Changelog

Upgrade FalkorDB Enterprise

Move to a newer addon release

Release channels

Platform components

Storage drivers

Tested upgrade paths

Admin components

Related