Tear down a kziti deployment

Use this procedure when you want to stop and remove a kziti-managed OpenZiti deployment from a host entirely. This applies to single-controller setups, individual HA members, and standalone private router hosts.

For removing a single HA controller while keeping the cluster running, see Remove an HA controller instead — you should run remove-member first, then teardown.

warning

--remove-data is destructive. It deletes the persistent OpenZiti state on the host (controller database, router certificates, identity material). Make sure you have any backups or exports you need before running with this flag.

Stop the stack only

To stop containers and remove the docker compose project, but keep the data directory in place:

kziti deploy uninstall --yes

This is appropriate when you are reinstalling on the same host and want to preserve state, or when you are inspecting state offline.

The data directory at /opt/kziti/data (or <install-dir>/data if you used a non-default --install-dir) is left intact.

Stop and wipe

To also remove the persistent data:

kziti deploy uninstall --remove-data --yes

This stops all containers, removes the docker compose project, and deletes the data directory. The host is left clean — only the kziti binary remains on PATH.

To remove the binary as well:

sudo rm /usr/local/bin/kziti