> ## Documentation Index
> Fetch the complete documentation index at: https://docs.falkordb.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> FalkorDB is a graph database that speaks the Redis protocol. Queries are issued as OpenCypher through the GRAPH.QUERY and GRAPH.RO_QUERY commands, not over Bolt or a SQL connection.
> FalkorDB implements a subset of OpenCypher with proprietary extensions. Do not assume Neo4j-only syntax or procedures are available — check /cypher/cypher-support and /cypher/known-limitations before using a clause.
> FalkorDB is the successor to RedisGraph, but they are separate products. Do not present RedisGraph commands, versions, or limitations as current FalkorDB behavior.
> Use the official clients listed in /getting-started/clients rather than generic Redis or Neo4j drivers, and prefer the language the user is already working in.
> Configuration parameters are set with GRAPH.CONFIG SET or at startup; cite the exact parameter name from /getting-started/configuration rather than inventing one.
> This site covers four products: FalkorDB (core), FalkorDB Cloud, FalkorDB Enterprise, and the GraphRAG SDK. Name which one an answer applies to, since setup and operations differ.

# Upgrade KubeBlocks

> Upgrade the KubeBlocks platform components used by FalkorDB Enterprise.

The default installer manages KubeBlocks as a separate Helm release in `kb-system`. It reads the desired KubeBlocks version from the Enterprise chart dependency unless `--kubeblocks-version` is provided.

## Prechecks

```bash theme={null}
helm status kubeblocks -n kb-system
kubectl get pods -n kb-system
kubectl get crd | grep kubeblocks
```

Back up current values and CRD inventory:

```bash theme={null}
helm get values kubeblocks -n kb-system -o yaml > kubeblocks.current-values.yaml
kubectl get crd -o name | grep kubeblocks > kubeblocks.crds.before.txt
```

Check current FalkorDB Enterprise releases and workloads:

```bash theme={null}
helm status falkordb-enterprise -n falkordb-system
kubectl get clusters.apps.kubeblocks.io -A
```

## Upgrade with the installer

```bash theme={null}
curl -fsSL https://falkordb.github.io/FalkorDB-Enterprise/install.sh | \
  bash -s -- \
    --kube-context production-cluster \
    --namespace falkordb-system \
    --kubeblocks-namespace kb-system \
    --kubeblocks-version '<kubeblocks-version>' \
    --values production-values.yaml \
    --yes
```

The installer applies KubeBlocks CRDs, installs or updates the KubeBlocks Helm release, installs or updates Snapshot Controller, and then upgrades the Enterprise release.

## Upgrade KubeBlocks only

If you need to upgrade KubeBlocks separately from Enterprise, use Helm directly with the same required RBAC override that the installer applies:

```bash theme={null}
helm repo add kubeblocks https://apecloud.github.io/helm-charts
helm repo update kubeblocks

kubectl apply --server-side -f "https://github.com/apecloud/kubeblocks/releases/download/v<kubeblocks-version>/kubeblocks_crds.yaml"
kubectl apply --server-side -f "https://raw.githubusercontent.com/apecloud/kubeblocks/v1.2.0-alpha.1/deploy/helm/crds/apps.kubeblocks.io_componentdefinitions.yaml"

helm upgrade --install kubeblocks kubeblocks/kubeblocks \
  -n kb-system \
  --create-namespace \
  --version '<kubeblocks-version>' \
  --set 'autoInstalledAddons={}' \
  --set 'rbac.additionalPolicyRules[0].apiGroups[0]=rbac.authorization.k8s.io' \
  --set 'rbac.additionalPolicyRules[0].resources[0]=clusterroles' \
  --set 'rbac.additionalPolicyRules[0].verbs={create,delete,get,list,patch,update,watch}' \
  --wait --timeout 20m
```

## Post-upgrade validation

```bash theme={null}
helm status kubeblocks -n kb-system
kubectl get pods -n kb-system
kubectl get clusters.apps.kubeblocks.io -A
kubectl get opsrequests.operations.kubeblocks.io -A
```

In the Admin UI, verify deployment list, deployment details, operations, backups, logs, and metrics.

## Rollback notes

KubeBlocks rollback can involve CRDs and conversion webhooks. Do not blindly roll back CRDs on a production cluster without checking KubeBlocks compatibility and current custom resources.

For the Helm release itself:

```bash theme={null}
helm history kubeblocks -n kb-system
helm rollback kubeblocks <revision> -n kb-system --wait --timeout 20m
```

After rollback, validate KubeBlocks pods, webhooks, CRDs, and existing FalkorDB clusters.