Skip to main content
Confirm each item below before running the installer. The installer performs a permission preflight check and prints an install plan, but it cannot provision capacity or open network egress for you.

​
Cluster capacity

At least 3 worker nodes.
4 CPU and 16 GB of memory per worker node.
A default StorageClass, ideally CSI-backed so volume snapshot backups work.
Kubernetes 1.27 or later is recommended. On OpenShift, use OCP 4.14 or later.

​
Local tooling

The machine that runs the installer needs: Verify the active context before installing:

​
Kubernetes permissions

Your Kubernetes user must be able to create:
  • Namespaces
  • CRDs
  • RBAC resources (ClusterRoles and bindings)
  • KubeBlocks resources
  • Namespace-scoped workloads, Services, Secrets, and PVCs
The installer verifies these permissions before it changes the cluster. Pass --skip-auth-check to bypass the check when your platform restricts SelfSubjectAccessReview.

​
Network access

The cluster needs outbound access to pull images from:
Every image above is also mirrored to registry.falkordb.cloud, so a cluster that can only reach that one host can still install the full stack. See Private registries.

​
Values to prepare

Production installs go faster if you collect these first:
  • Kubernetes context name
  • FalkorDB Enterprise namespace and KubeBlocks namespace
  • Public Admin UI hostname
  • TLS certificate or cert-manager issuer for that hostname
  • A stable JWT secret of at least 32 characters — generate one with openssl rand -hex 32
  • Image pull credentials for registry.falkordb.cloud
  • A signed FalkorDB Enterprise license
  • Storage class for Admin Server persistence, if the cluster default is not suitable
  • The CSI driver name backing that storage class, for volume snapshot backups

​
Next step

Quickstart

Install the default stack and sign in to the Admin UI.