Uninstall the Neo4j cluster and clean up the created resources

1. Uninstall all Neo4j Helm deployments

  1. Uninstall each of the cluster members (both the cores and read replica) and the services using their Helm release names:

    helm uninstall core-1 core-2 core-3 rr-1 lb headless
    release "core-1" uninstalled
    release "core-2" uninstalled
    release "core-3" uninstalled
    release "rr-1" uninstalled
    release "lb" uninstalled
    release "headless" uninstalled

2. Fully remove all the data and resources

Uninstalling the Helm releases does not remove the created resources and data. Therefore, after uninstalling the helm deployments, you also have to delete all the data and resources.

  1. Display all data associated with each of the GCP persistent disks you have created, for example:

    gcloud compute disks describe "core-disk-1"

    If you re-create Neo4j with the same settings, it will pick up the same disk again, and all the data will still be on it.

    Even if the GKE cluster is deleted, the persistent disks with the Neo4j data will still exist.

  2. Delete each of the GCP persistent disks you have created in Create a persistent volume for each cluster member using the following command and the name of the disk, for example:

    gcloud compute disks delete core-disk-1
    The following disks will be deleted:
     - [core-disk-1] in [europe-west6-c]
    Do you want to continue (Y/n)?  y
    Deleted [https://www.googleapis.com/compute/v1/projects/neo4j-helm/zones/europe-west6-c/disks/core-disk-1].

    If you want to delete the entire GKE Kubernetes cluster, run:

    gcloud container clusters delete my-neo4j-gke-cluster
  1. Display all data associated with the AWS EBS disks by running:

    aws ec2 describe-volumes --filters Name=tag:volume,Values=core-disk-1,core-disk-2,core-disk-3,rr-disk-1 --query "Volumes[*].{ID:VolumeId}" --output text

    If you re-create Neo4j with the same settings, it will pick up the same disk again, and all the data will still be on it.

    Even if you delete the EKS cluster, the EBS disks with the Neo4j data will still exist. Note that the disk will be deleted if its Resource Group is deleted.

  2. Delete each of the AWS EBS disks you have created in Create a persistent volume for each cluster member using the following command and the volume ID, for example:

    aws ec2 delete-volume --volume-id "<volume id>"

    If you are sure that you want to delete the entire EKS Kubernetes cluster, run:

    eksctl delete cluster my-neo4j-eks-cluster
  1. Display all data associated with the Azure managed disks by running:

    az disk show --name "core-disk-1"

    If you re-create Neo4j with the same settings, it will pick up the same disk again and all the data will still be on it.

    Even if you delete the AKS cluster, the managed disk with the Neo4j data will still exist. Note that the disk will be deleted if its Resource Group is deleted.

  2. Delete each of the Azure managed disks you have created in Create a persistent volume for each cluster member using the following command and the disk name, for example:

    az disk delete --name "core-disk-1"

    If you are sure that you want to delete the entire AKS Kubernetes cluster, run:

    az aks delete --name my-neo4j-aks-cluster