Skip to main content
This page summarizes the high-impact Helm values for FalkorDB Enterprise.
The source of truth is helm/falkordb-enterprise/values.yaml. Verify against the chart version you are installing.

Platform dependencies

When using scripts/install.sh, the installer detects the default StorageClass provisioner and configures snapshot values automatically:
  • CSI-backed cloud StorageClasses, such as ebs.csi.aws.com, pd.csi.storage.gke.io, and disk.csi.azure.com, get a matching chart-managed VolumeSnapshotClass unless a default one already exists for that driver.
  • Local non-CSI StorageClasses, such as rancher.io/local-path, enable the optional csi-hostpath-driver and make csi-hostpath-sc the default for new PVCs. Existing PVCs are not migrated.
  • Unknown or non-CSI provisioners disable the chart-managed VolumeSnapshotClass; pass --set volumeSnapshotClass.driver=<csi-driver> when the storage platform supports snapshots but cannot be detected.
Explicit --set and --set-string values passed to the installer override the detected snapshot configuration. On upgrades, the installer reuses existing Helm release values before applying new detected values. This preserves deployment-specific image tags, image pull secrets, ingress hosts, TLS settings, and immutable PVC settings while still adding the correct snapshot configuration. FalkorDB Enterprise is intentionally limited to one installation per Kubernetes cluster. The chart renders a fixed cluster-scoped ClusterRole install lock and also checks for an existing Helm-owned ClusterDefinition/falkordb from older chart versions. Upgrades of the owning Helm release are allowed; installs from a different release or namespace fail during Helm rendering.

Gateway and public URLs

Admin Server

Admin Server license

Leave adminServer.license unset to start on a 14-day free trial with no configured limits — no license value or Secret is required. Activate or replace the license later from the Admin UI’s License page; the values below only matter if you want to provide a license at install time.
Set a license directly in values for development or one-off installs:
For production, store the signed license in an existing Secret in the release namespace and reference it from values:
The admin server reads the Secret through FALKORDB_LICENSE, validates the signature, and persists the license state at adminServer.license.statePath. If the license expires, is invalid, or any configured limit is exceeded, the server and UI enter read-only mode until a valid license within limits is active. The signed license key payload includes a version field so future payload formats can be introduced explicitly. The current supported payload version is 1. To bind a license to one Kubernetes cluster, include k8sClusterId in the signed payload. By default the admin server compares this value to the UID of the kube-system namespace. You can retrieve it with:
If your environment needs a different cluster identity source, set K8S_CLUSTER_ID on the admin server and issue licenses with the same value. Licenses without k8sClusterId remain unbound.

Bootstrap Admin resources

Admin UI

Browser encryption

Observability