clean-uninstall

Uninstalling the Quanton Operator from Kubernetes requires removing the Helm release, deleting associated secrets across namespaces, and removing the custom resource definition (CRD) to ensure no remnants remain.

The Quanton Operator CRD remains after Helm uninstall because Helm does not automatically delete custom resource definitions by default. Manual removal of the CRD and created secrets is required for full cleanup.

Yes, you need both kubectl and helm to remove the Quanton Operator. Helm uninstalls the chart release, while kubectl deletes remaining secrets and the custom resource definition from the Kubernetes cluster.

The best way to clean up leftover Kubernetes secrets from an operator is using a dedicated cleanup process that deletes the Helm release and explicitly removes associated secrets and CRDs across namespaces for complete removal.

Yes, you can remove the Quanton Operator CRD without affecting other Helm deployments. The cleanup targets only the Quanton Operator release, associated secrets, and its specific CRD, leaving other deployments untouched.