Uninstall SigNoz
This document outlines the steps to uninstall SigNoz, covering various deployment methods such as Docker Standalone, Docker Swarm, and Kubernetes.
Docker Standalone
To uninstall SigNoz installed via Docker Standalone, use the following command:
docker compose down -v
This command will stop and remove all containers, networks, and volumes associated with the SigNoz deployment.
Docker Swarm
To uninstall SigNoz deployed on Docker Swarm, use the following command:
docker stack rm signoz
This command will remove all services and resources associated with the SigNoz stack.
Kubernetes
To uninstall SigNoz deployed on Kubernetes using Helm, follow these steps:
Uninstall Helm Release: This command removes all Kubernetes components associated with the Helm chart and deletes the release, except for ClickHouse CRD resources.
helm -n <namespace> uninstall "<release-name>"
Refer to the Helm docs for more details on the
helm uninstall
command.Delete ClickHouse CRD Resources: If you are using ClickHouse managed by SigNoz, you might need to manually remove finalizers from ClickHouse CRD resources to ensure their complete deletion.
kubectl -n <namespace> patch \ clickhouseinstallations.clickhouse.altinity.com/<release-name>-clickhouse \ -p '{"metadata":{"finalizers":[]}}' --type=merge
Delete Persistent Volume Claims (PVCs): The uninstallation process may not automatically delete associated PVCs. To clean them up, use the following command:
kubectl -n <namespace> delete pvc -l app.kubernetes.io/instance=<release-name>
Delete Namespace: Finally, delete the namespace where SigNoz was installed:
kubectl delete namespace <namespace>
Last updated: August 21, 2025
Edit on GitHub