None of this is reversible. Read the order before running any of it.
Remove one node
Delete the server or move it elsewhere first, then delete the node in Settings → Nodes. Deleting the node record neither stops the Agent nor frees the disk. Both of those happen on the host.
Linux:
sudo systemctl disable --now kraken-agent
sudo rm -f /etc/systemd/system/kraken-agent.service
sudo systemctl daemon-reload
sudo rm -rf /opt/kraken/bin /usr/local/bin/kraken-agent /etc/kraken/agent.env
# state, server data and local backups — check before you run this
sudo rm -rf /var/lib/krakenWindows:
C:\kraken\bin\kraken-agent.exe --service stop
C:\kraken\bin\kraken-agent.exe --service uninstall
Remove-NetFirewallRule -DisplayName "Kraken Agent (TCP 9090 gRPC + 2022 SFTP)"
# binaries, state, server data and backups — check before you run this
Remove-Item -Recurse -Force C:\krakenGame containers the Agent created stay on the host's Docker daemon. Remove them yourself if you want the space back:
docker ps -a --filter "name=kraken-" Remove the Panel: compose
docker compose --env-file deploy/.env -f deploy/docker-compose.full.yml downThat keeps the volumes. To delete the fleet with them:
docker compose --env-file deploy/.env -f deploy/docker-compose.full.yml down -v-v destroys pgdata (every server, node, user and audit row) and
panel-state (the config file, the generated CA, the secrets key if it was
generated rather than supplied). No prompt, no undo.
Remove the Panel: bare metal
sudo systemctl disable --now kraken-panel
sudo rm -f /etc/systemd/system/kraken-panel.service
sudo systemctl daemon-reload
sudo rm -f /usr/local/bin/kraken-panel /usr/local/bin/kraken-krakenctl
sudo rm -rf /etc/kraken /var/lib/kraken
sudo userdel krakenPostgres is separate: either a container you brought up from
deploy/docker-compose.yml, or a database of your own. Drop it deliberately.
What is left behind
- Cloudflare DNS records and UniFi port forwards the integrations created are not removed by uninstalling. They live in those systems; delete them there.
- Router port forwards you made by hand for game ports.
- Off-node backups on a NAS share or SFTP remote. Kraken never reaches back to clean them up, which is the behaviour you want right up until you forget they are there.