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

# Uninstall

> Remove FalkorDB Enterprise and, optionally, the platform components it installed.

## Preview the plan

The uninstall script supports dry-run mode:

```bash theme={null}
bash scripts/uninstall.sh --dry-run
```

For a specific context and namespace:

```bash theme={null}
bash scripts/uninstall.sh \
  --kube-context production-cluster \
  --namespace falkordb-system \
  --dry-run
```

## Uninstall Enterprise only

This removes the FalkorDB Enterprise Helm release and retained FalkorDB addon resources. KubeBlocks is kept.

```bash theme={null}
bash scripts/uninstall.sh \
  --namespace falkordb-system
```

For automation:

```bash theme={null}
bash scripts/uninstall.sh \
  --namespace falkordb-system \
  --yes
```

## Also uninstall KubeBlocks

```bash theme={null}
bash scripts/uninstall.sh \
  --namespace falkordb-system \
  --kubeblocks-namespace kb-system \
  --uninstall-kubeblocks
```

## Delete namespaces

```bash theme={null}
bash scripts/uninstall.sh \
  --namespace falkordb-system \
  --kubeblocks-namespace kb-system \
  --uninstall-kubeblocks \
  --delete-namespaces
```

If `--uninstall-kubeblocks` is not provided, `--delete-namespaces` deletes only the Enterprise namespace.

## Delete CRDs

Deleting CRDs removes KubeBlocks and VolumeSnapshot API definitions from the cluster. This can affect other workloads that use those APIs.

```bash theme={null}
bash scripts/uninstall.sh \
  --uninstall-kubeblocks \
  --delete-crds \
  --yes
```

## Verify removal

```bash theme={null}
helm status falkordb-enterprise -n falkordb-system
kubectl get all -n falkordb-system
```

If KubeBlocks was removed:

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

If namespaces were deleted:

```bash theme={null}
kubectl get namespace falkordb-system kb-system
```