Sharded deployment - FalkorDB Enterprise

When to use this

Use sharded topology for workloads that need to distribute data and traffic across multiple shards. The Admin UI maps this flow to:

spec.topology: cluster
spec.replicas as replicas per shard
spec.sharding.enabled: true
spec.sharding.shardCount from the shard count field
spec.sharding.replicas as replicas per shard

Create with quick create

Open Deployments > Create Deployment.
Choose Sharded.
Choose Dev, QA, or Prod.
Choose Quick Create.
Enter name, namespace, and FalkorDB version.
Submit.

Create with full setup

Open Deployments > Create Deployment.
Choose Sharded.
Choose Full Setup.
Complete the wizard:
- General: name, namespace, version, termination policy, labels.
- Component: shard count, replicas per shard, CPU, memory, storage class, storage size, node affinity.
- Configuration: optional FalkorDB runtime parameters.
- Authentication: ACL username/password or LDAP where supported.
- Encryption: optional TLS configuration.
- Networking: optional service for the sharding component, and an optional external domain for stable per-pod DNS names outside the cluster. See Networking.
- Backup: optional backup repository and cron schedule.
- Review: submit.

Verified defaults and constraints

Field	Default or constraint
Shard count	`3`
Replicas per shard	`1` for Dev, `2` for QA/Prod
Storage	`10Gi`
Backup schedule	`0 2 * * *` when backup is enabled
CPU minimum sent to API	`250m` for shard resources
Memory minimum sent to API	`100Mi` for shard resources

Prod enforces at least 2 replicas per shard.

Validate

kubectl get clusters.apps.kubeblocks.io -n <namespace>
kubectl get pods -n <namespace>

In the Admin UI, open General to confirm shard count and replicas per shard, then review Pods, Metrics, and Operations.

⌘I