Skip to main content

Uninstall RisingWave from a Kubernetes cluster

This topic describes how to uninstall RisingWave from a Kubernetes cluster with Helm and how to remove the persistent volume claims (PVCs) and data in object stores.

Uninstall RisingWave from a K8s cluster with Helm

To gracefully uninstall RisingWave from a Kubernetes cluster with Helm:

helm uninstall my-risingwave

Then wait for the uninstallation to complete. You can monitor the uninstallation status by using this command:

kubectl get pods

Delete the persistent volume claims

To check the persistent volume claims, use the following command:

kubectl get persistentvolumeclaims -l app.kubernetes.io/instance=my-risingwave

If there are any existing persistent volume claims, you can delete them using the following command:

kubectl delete persistentvolumeclaims -l app.kubernetes.io/instance=my-risingwave

Please note that the underlying persistent volumes will be reclaimed based on their reclaim policies. For more information, you can refer to the documentation.

Delete the data in object storage

If you configure AWS S3 or other object storage options from cloud service providers as the state backend, you should also delete the bucket to avoid conflicts when deploying a new cluster with the same bucket name.

Help us make this doc better!