search

RedHatGov / devsecops-workshop-dashboard

15 stars 13 forks source link

Uninstalling DevSecOps Operator does not remove other operators #20

Open dmc5179 opened 3 years ago

dmc5179 commented 3 years ago

DevSecOps Operator provisions several other operators. When uninstalling the DevSecOps operator, the other operators, like code ready workspaces, remain. The instances of those operators, like the code ready pods for each user, also remain. At least the deployments of those operators for workshop users should be removed with the DevSecOps operator is removed.

dmc5179 commented 3 years ago

Even after removing all of the operators installed by the DevSecOps operator, pods for code ready workspaces remain, rocketchat remains.

jflowers commented 3 years ago

Removing an operator does not remove the operands. To remove the operands you must first delete the CR that defined them.

andykrohg commented 3 years ago

Looks like @dmc5179 did remove the DevSecOpsWorkshop CR. The existence of orphaned resources after the CR is deleted is a known issue - the finalizer doesn't remove template-based applications (such as rocket chat) or dependent operators at the moment.

jflowers commented 3 years ago

Ooh, sorry, my bad