Skip to main content
install.sh installs or updates FalkorDB Enterprise on any Kubernetes cluster reachable by kubectl. It prints an install plan and asks for confirmation before changing the cluster. Both scripts are published at https://falkordb.github.io/FalkorDB-Enterprise/, so no repository checkout is needed.
Confirmation prompts are read from /dev/tty, so the piped form above stays interactive.
Every long option has an environment variable equivalent in uppercase with underscores. For example, --kube-context maps to KUBE_CONTEXT and --namespace maps to NAMESPACE. The registry credentials are the exception: --registry-server, --registry-username and --registry-password map to IMAGE_PULL_SECRET_SERVER, IMAGE_PULL_SECRET_USERNAME and IMAGE_PULL_SECRET_PASSWORD.

Release and namespace options

Chart options

Secrets and registry options

A credential typed on the command line, as a flag or as a VAR=value prefix, lands in your shell history. To keep it out, read it at a prompt and export it, then run the installer without the password flag: read -rsp 'Registry token: ' IMAGE_PULL_SECRET_PASSWORD && export IMAGE_PULL_SECRET_PASSWORD, then ... | bash -s -- --registry-username '<username>' --yes. The same works for JWT_SECRET.

Platform dependency options

Networking options

Leave the last two unset on a normal cluster. They are only needed where the ClusterIP route fails — a managed or public API endpoint that requires SNI (connecting by IP sends no SNI, so TLS fails mid-handshake), or a firewall that rejects the ClusterIP. Use a DNS name covered by a SAN on the API server’s certificate, such as kubernetes.default.svc.cluster.local; an uncovered name fails certificate verification instead. See Helm values for the underlying keys.

Execution options

Examples

Uninstall

uninstall.sh removes the Enterprise release and, optionally, the platform components the installer added. It refuses to run while FalkorDB deployments exist unless you pass --force, keeps the backup repository and, unless --delete-namespaces deletes its namespace, the bootstrap admin user, and makes the StorageClass the installer demoted the cluster default again. See the uninstall playbook for the full procedure and data-retention considerations.

Source of truth

The installer help text is authoritative. Run it to see the exact options for your version: