oz0 node upgrade
For: Operators and developers looking up a command.
Tell nodes which runtime version to run. A node starts the new version next to the one it runs, new jobs move to it once most of the tenant's nodes run it, and the old version stops when no job is pinned to it any more. --runtime "" lets the nodes keep what they run.
--binary tells nodes to replace their own binary with the one the edge serves: each node checks the release's signature against the keys it trusts, swaps the binary, and restarts its runtimes. It takes only a release on the channel the cluster follows, and never an older one than it runs: --allow-older with --reason lets nodes go back, and only a cluster admin may pass it.
Management signs that allowance, a node checks the signature, and it holds for seven days and takes each node back once.
Usage
oz0 node upgrade [node-id...] [flags]
Flags
| Flag | Type | Default | Description |
|---|---|---|---|
--all-in | string | every accepted node of this tenant | |
--allow-older | bool | with --binary, let nodes go back to an older release than they run (cluster admins only; needs --reason) | |
--binary | bool | replace the node binary with the one the edge serves, signed | |
--json | bool | print JSON instead of a table | |
--reason | string | why nodes go back, for the audit log (with --allow-older) | |
--runtime | string | the runtime version to run: one the edge serves |
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.