From fea3ecfe86c02555b667dbc5d5bfe014d5561a21 Mon Sep 17 00:00:00 2001 From: Heiko Kiesel Date: Wed, 6 Sep 2023 11:37:59 +0200 Subject: [PATCH] #1101 Clarify documentation that scans and hooks/scanners must be deleted before the operator Signed-off-by: Heiko Kiesel --- documentation/docs/getting-started/uninstallation.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/documentation/docs/getting-started/uninstallation.md b/documentation/docs/getting-started/uninstallation.md index 6e8a576624..af215f7862 100644 --- 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