Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Weltraumschaf merged 1 commit into from
Sep 6, 2023
Merged

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

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion documentation/docs/getting-started/uninstallation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down