Skip to content
These docs are a preview of Self-Managed Kindo 2026.11, an upcoming release.

Uninstall Kindo

Terminal window
kindo uninstall all

Uninstalling removes what installing created in the cluster, including the Qdrant, ClickHouse, and HyperDX data, but keeps the config. Your external databases, your object storage, and an External Secrets Operator the Kindo CLI didn’t install stay as they are.

To remove only Kindo’s applications:

Terminal window
kindo uninstall applications

To remove only the supporting services:

Terminal window
kindo uninstall peripheries

To keep the data volumes, remove the namespaces, or run without asking, see kindo uninstall.

When the uninstall can’t remove part of Kindo, it names what it left and ends with an error instead of reporting that it completed. For the integrations service, which the uninstall removes even after every integration is turned off, it also names the command that removes it. Run that command, then run the uninstall again.

An uninstall that removed the namespaces leaves the External Secrets Operator the Kindo CLI installed, and the sandbox CRDs, in place while resources that don’t belong to Kindo still use them. It lists what it found. Delete or move those, then run the uninstall again.

When the config doesn’t validate, for example after a config setting was renamed, the uninstall still removes Kindo’s components and warns that it read only part of the config. A component whose value it can’t read is kept like any other turned-off component.

If the uninstall can’t read the registry or the integrations, the config isn’t valid YAML, or the registry login fails, it removes nothing. It then accepts only one of these commands:

Terminal window
kindo uninstall all --delete-namespaces
kindo uninstall all --keep-data