Uninstalling

telark is one Helm release, so removing it is one command — but the custom resources deliberately outlive it.

1. Quiesce first

1. Cancel or let expire any active protection plan. Uninstalling with a plan active leaves its admission policies behind until the policy engine is removed too.
2. Wait for any in-progress rollback to finish or fail. The controller will not resume one after the pods are gone.

2. Uninstall the release

helm uninstall telark -n telark

3. Decide what to keep

CRDs and every existing telark custom resource are not removed: they carry helm.sh/resource-policy: keep, so reinstalling the chart picks up where you left off. The exporter's snapshot PVC survives for the same reason.

For a full teardown — this also deletes every telark custom resource in the cluster:

kubectl delete crd -l app.kubernetes.io/part-of=telark
kubectl delete namespace telark

Export anything you want to keep first. See Operations → Backups for the kubectl get commands that capture each resource.

Related

• Guides → Installing into a new cluster
• Operations → Backups