NetApp
Trident operator doesn't clean up during uninstall when using 'Uninstall Operator' in OpenShift console
Describe the bug Uninstalling the Trident Operator from the OpenShift console using the 'Uninstall Operator' in 'Installed Operators' deletes most of the Trident objects except for:
- trident-operator.openshift-operators
- tridentconfigurators.trident.netapp.io
- tridentorchestrators.trident.netapp.io
Environment Red Hat OpenShift Services on AWS Client Version: 4.17.9 Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3 Server Version: 4.17.9 Kubernetes Version: v1.30.6 trident-operator.v24.10.0
- Trident version: trident-operator.v24.10.0
- Trident installation flags used: deployed
- NetApp backend types: FSxN
To Reproduce Steps to reproduce the behavior:
- Deploy the Trident Operator from the 'OperatorHub'
- Delete the Trident Operator from the 'Installed Operators'
Expected behavior No more Trident objects left behing.
Additional context n/a
Those resources are not managed by the Trident operator, but by OLM. Uninstalling the operator does not remove CRDs or the operator CR, to prevent data loss: https://olm.operatorframework.io/docs/tasks/uninstall-operator/. The cluster admin is able remove those resources if they aren't worried about losing data.
