#general

Uninstalling Signoz - Issue with Deleting ClickHouse PVC Volumes

TLDR Vinay faced issues while uninstalling Signoz. Prashant suggested patching the PVCs to resolve, which worked successfully.

Join the chat

May 26, 2023 (3 days ago)

Photo of md5-5aa2a78b8c6b3b9f0284363d85b74cfa

Vinay

07:16 AM

Hi all,
when am trying to uninstall Signoz as per the instructions provided in https://signoz.io/docs/operate/kubernetes/#uninstall-signoz-cluster, unable to delete click house PVC volumes?

Image 1 for Hi all,<br>when am trying to uninstall Signoz as per the instructions provided in <a href="https://signoz.io/docs/operate/kubernetes/#uninstall-signoz-cluster" target="_blank">https://signoz.io/docs/operate/kubernetes/#uninstall-signoz-cluster</a>, unable to delete click house PVC volumes?

Photo of md5-1899629483c7ab1dccfbee6cc2f637b9

Prashant

11:48 AM

Vinay This mostly happens when you try to delete the volumes prior to properly deleting the ClickHouse Instance i.e. chi resource.

You can resolve this by patching the PVCs in the namespace:

kubectl get -n platform pvc -o=name | xargs kubectl patch \
  -n platform \
  -p '{"metadata":{"finalizers":[]}}' --type=merge

11:48

Prashant

11:48 AM

^ replace platform with your custom namespace

Vinay

12:42 PM

Thanks, Prashant - it worked..!!!

SigNoz Community

Built with ClickHouse as datastore, SigNoz is an open-source APM to help you find issues in your deployed applications & solve them quickly | Knowledge Base powered by Struct.AI

Join Our Community

Similar Threads

Deploying SigNoz with Kubernetes - Stuck in Pods

Dedy experienced issues while deploying SigNoz with Kubernetes, as the pods were stuck. Prashant identified missing CHI pods as the cause and suggested trying `helm upgrade`.

1mo

SigNoz Deployment Issue with External ClickHouse and PVC

Ragulraj faced issues with deploying SigNoz v0.18.1 through kubernetes due to otel-collector not connecting to the correct ClickHouse cluster. After discussing with Srikanth, Syed and Prashant, he decided to try again with SigNoz helm charts, but faced issues with PVC remaining pending.

1mo

Issues with Signoz on k3s Cluster Using Helm

Nilanjan encountered issues with Signoz on a k3s cluster using Helm, with some pods not running. Srikanth and Prashant suggested using `kubectl describe` to diagnose the issue, but the problem remains unresolved.

2mo

Issues with SigNoz Install through Helm Chart

Romain experienced a delay in SigNoz installation through Helm Chart, with pods in init state. Prashant identified the issue as insufficient resources in the K8s cluster and suggested specifying a storage class for PVCs, resolving the problem.

2mo

Signoz Installation Error in Kubernetes Cluster

Nilanjan faced a ClickHouse image pull error with a Kubernetes install. Prashant identified it as an issue in the user's cluster. Creating a new cluster resolved the problem.

2mo