Uninstall

How to uninstall Nsight Operator.

Uninstalling Nsight Operator

helm uninstall nsight-operator -n nsight-operator

helm uninstall removes the Deployments, Services, ConfigMaps, RBAC, and the default CRs created by the chart.

Note

In multi-tenant mode, tenant namespaces may hold auto-provisioned or manually deployed CRs (NsightCoordinator, NsightGateway, etc.) that are independent of the Helm release. See Quickstart Example (Multitenant Mode) for tenant-side cleanup.

Reclaiming storage

helm uninstall does not delete PersistentVolumeClaims created by StatefulSets (MinIO when persistence is enabled, the OTel collector). Delete them manually to reclaim the underlying storage.

Warning

Deleting these PVCs is irreversible and permanently destroys their contents – including MinIO-hosted .nsys-rep profiling reports and any buffered OTel collector data. Before running the command below, confirm the reports are no longer needed, or back up the data to external S3 / a different cluster. There is no helm rollback for PVC contents once they are deleted.

kubectl delete pvc -l app.kubernetes.io/name=nsight-operator -n nsight-operator

Removing the Dynamo helper configuration

If you used nsight_operator_dynamo.py to install (single-tenant) or configure (multi-tenant) a namespace, run the matching teardown subcommand in addition to helm uninstall so that Dynamo-managed resources – the NsightOperatorProfileConfig CR, the GPU-metrics DaemonSet and its ConfigMap, and any tenant-namespace Secrets / ConfigMaps the script created – are removed:

# Single-tenant
python3 nsight_operator_dynamo.py -n nsight-operator uninstall

# Multi-tenant (per tenant namespace)
python3 nsight_operator_dynamo.py -n <tenant-ns> unconfigure

If you only used the Helm chart (no Dynamo helper), helm uninstall on its own is sufficient.