oz0 node purge
Purge nodes (plan §12).
For: Operators and developers looking up a command.
Purge nodes (plan §12). Each loses access to work at once. On its next control stream, which a blocked or offline node gets too when it comes back, it receives a command signed with the cluster CA's key, checks the signature, stops its runtimes and plugins, deletes its data directory (keys, plugins, runtimes and tools) and its binary, and is forgotten. The machine must be set up again to rejoin.
Usage
oz0 node purge <node-id>... --yes [flags]
Flags
| Flag | Type | Default | Description |
|---|---|---|---|
--yes | bool | confirm that the nodes are to delete themselves |
Inherited flags
| Flag | Type | Default | Description |
|---|---|---|---|
--context | string | $OZ0_CONTEXT or <config dir>/orchestrator-zero/context.json | CLI context file written by server init |
--log-level | string | info | log level: debug, info, warn or error |
See all oz0 commands and the global flags.