#1101 Clarify documentation that scans and hooks/scanners must be deleted before the operator

Heiko Kiesel · Heiko Kiesel · commit fea3ecfe86c0 · 2023-09-06T11:37:59.000+02:00
Signed-off-by: Heiko Kiesel &lt;heiko.kiesel@iteratec.com&gt;
diff --git a/documentation/docs/getting-started/uninstallation.md b/documentation/docs/getting-started/uninstallation.md
@@ -31,7 +31,10 @@ kubectl delete cascadingrules.cascading.securecodebox.io nmap-hostscan
 
 To uninstall the operator it is not enough to delete the operator via `helm` because the operator creates Roles, ServiceAccounts and RoleBindings used by parsers, lurkers and hooks in every namespace where scanners and hooks are executed. These cannot be uninstalled via helm because they cannot be referenced via Kubernetes OwnerReferences.
 
-Make sure you delete all scans and uninstall all scanners/hooks before uninstalling the operator to avoid problems.
+:::caution
+Make sure you delete **all scans** (finished and pending!) and uninstall all scanners/hooks before uninstalling the operator to avoid problems.
+:::
+
 First delete the namespace for the operator:
 
 ```bash
