Skip to main content
Everything you do after your workspace is running. Commands assume the default namespace tracebloc — substitute yours if you changed it.
Day-to-day management — inspecting the cluster, ingesting and removing data — is easiest with the tracebloc CLI. The Helm/kubectl commands here cover the lifecycle bits the CLI doesn’t (upgrade, stop/start, uninstall) and deeper debugging.

​
Which version am I on?

The install summary also prints the version, and --diagnose reports it on its first line.

​
Health & status

Then check your clients page — your workspace should read Online.

​
Logs

​
Stop & start (local / k3d)

Free up your machine without losing anything — data persists between stops.

​
Upgrade

The auto-upgrade CronJob keeps your workspace current by default. To upgrade manually:
--reset-then-reuse-values preserves the values the installer applied. Append --version <x.y.z> to pin a specific release.

​
Roll back

​
Move to another machine

The client’s identity is its Client ID, not the machine. To relocate: run the installer on the new host with the same Client ID, then re-ingest your datasets (or copy ~/.tracebloc). The old host can be uninstalled once the new one shows Online.

​
Uninstall

PVCs are annotated helm.sh/resource-policy: keep, so your data survives an uninstall. To remove it too: kubectl delete pvc --all -n tracebloc.

​
Back up

Your data lives in the data PVCs (or ~/.tracebloc on a local install). Back up that directory / those volumes on your normal schedule — tracebloc keeps nothing of yours off your infrastructure.