> ## 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 a FalkorDB version

> Update a deployment to a target FalkorDB version.

## What the UI does

The deployment details page opens an **Upgrade Deployment** dialog. The user enters a target version, and the UI calls:

```text theme={null}
POST /api/clusters/<clusterName>/upgrade?namespace=<namespace>
```

with this body:

```json theme={null}
{ "version": "<target-version>" }
```

The Admin Server validates the requested version against the version catalog, checks that the cluster exists, rejects upgrades for clusters in `Failed` state, and updates the cluster version.

## Upgrade from Admin UI

1. Open **Deployments**.
2. Open the target deployment.
3. Select **Upgrade**.
4. Enter the target FalkorDB version, for example `v2.0.0` or another version shown by your version catalog.
5. Select **Confirm Upgrade**.

The UI warns that the deployment will undergo a rolling restart and brief downtime may occur.

## Validate

```bash theme={null}
kubectl get clusters.apps.kubeblocks.io -n <namespace> <deployment-name> -o yaml
kubectl get pods -n <namespace>
kubectl get events -n <namespace> --sort-by=.metadata.creationTimestamp
```

In the Admin UI, review **General**, **Pods**, **Operations**, and **Events**.

## Failure handling

* If the version is invalid or unavailable, the backend returns a `400` response.
* If the cluster is not found, the backend returns a `404` response.
* If the cluster is in `Failed` state, resolve the cluster condition before retrying.

Rollback is not a separate UI flow today. To roll back, run another upgrade to the previously working FalkorDB version after confirming the version is available in the catalog.