Skip to main content

Prerequisites

  • Google Cloud CLI (gcloud), authenticated with gcloud auth login.
  • A GCP project with billing enabled and permissions to create GKE clusters, node pools, and firewall rules.
  • kubectl, helm, and base64 on the machine that runs the installer.
  • At least 3 worker nodes with 4 CPU and 16 GB of memory each.
  • Outbound access from the cluster to pull images: registry.falkordb.cloud (Enterprise images, credentials required), docker.io, apecloud-registry.cn-zhangjiakou.cr.aliyuncs.com, registry.k8s.io, and ghcr.io — or registry.falkordb.cloud alone, since every image is also mirrored there (see Private registries).
Select the project and enable the required API:

Required infrastructure

A production GKE install needs: Set common variables used by the commands below:

1. Create the GKE cluster

Create a regional Standard cluster with a small system node pool:
Notes:
  • --release-channel regular pins the cluster to a supported, tested Kubernetes version.
  • The Compute Engine persistent disk CSI driver and VolumeSnapshot support ship enabled by default on current GKE versions.

2. Create a node pool for databases

Size this pool for your FalkorDB memory footprint. Memory-optimized n2-highmem machines are a good fit for graph workloads.

3. Get cluster credentials

4. Verify storage and snapshot support

FalkorDB Enterprise uses persistent volumes for databases and the Admin Server, and volume snapshots for backups. Verify GKE defaults:
GKE ships the standard-rwo (balanced persistent disk) and premium-rwo (SSD persistent disk) storage classes, with standard-rwo marked default. Use premium-rwo for database volumes in production. If the volumesnapshots CRD already exists and a snapshot controller is active, skip the installer’s bundled one with --skip-snapshot-controller. Otherwise leave the default enabled.

Install FalkorDB Enterprise

Quick install

With the GKE context active, run the installer:
On a default GKE install, the installer deploys ingress-nginx (unless the cluster already has a default IngressClass), exposes the Admin UI and Admin Server API on a single public IP through the gateway Ingress, and prints the URL. See Quickstart for what the installer does and how to validate it.

Production install

For production, prepare a values file with TLS ingress, a stable JWT secret, and a bootstrap admin user as described in Production install. A ready-to-edit GKE example is available at helm/falkordb-enterprise/examples/values-gke.yaml. Example GKE-specific values:
Then install:

DNS

Point your Admin UI hostname at the ingress public IP:
Create an A record for admin.example.com pointing at the ADDRESS shown, either in your DNS provider or in Cloud DNS:

Validate the install

Open the Admin UI URL and sign in with the bootstrap admin user. For OAuth sign-in, see Google OAuth setup.

Clean up

Delete the Enterprise release first (see uninstall), then remove the GKE cluster:
Deleting the cluster removes its node pools, disks, and load balancers.