Skip to main content
Uninstalling removes SeekrFlow from the cluster. To protect your data, it keeps some resources in place. See Remove retained resources.

Uninstall

1

Preview the uninstall

2

Uninstall

sfe asks you to confirm. It removes the resources SeekrFlow created while it ran, then uninstalls the release. If it stalls, add --force to finish. A forced uninstall can leave resources behind.

Remove retained resources

The uninstall keeps these resources, so that uninstalling by mistake doesn’t destroy data. To reinstall after a failed first install, remove the namespaces and databases, then start again from Create the namespaces. Reuse your values file rather than running sfe bootstrap again.
Removing these resources is permanent, and destroys your deployment’s data. Remove them only if you want the deployment gone entirely. To keep a copy of the databases, back them up first. See Back up the databases.

Delete the custom resource definitions

Deleting a custom resource definition deletes every resource of that kind across the whole cluster, not only in the seekrflow namespace. Skip any definition that other software on the cluster uses.

Drop the databases and roles

If you created the PostgreSQL instance only for SeekrFlow, delete the instance instead. If other applications use it, drop only SeekrFlow’s databases and roles. Connect to the postgres database as your admin account, then run these statements. If you didn’t enable Keycloak, the keycloak statements do nothing:
Last modified on October 16, 2026