oz0-node release-channel
For: Operators and developers looking up a command.
A node learns the channel it was installed on from the signed release it runs, and keeps it in its data directory. The cluster's channel, which the edge tells nodes, can only narrow it: a node refuses a release of a channel its installed channel does not take, and so a runtime from one, whatever the edge says, because whoever controls an edge must not move a fleet to another line of signed releases.
When the cluster itself moves to another channel, run this on each node's machine first: stable, preview or lts-<major>.<minor>. A running node reads it at its next update; one that refused a release already is told again when it connects, so restart it. Give the data directory the node runs with: a service's is not the one your own account gets by default.
Usage
oz0-node release-channel [CHANNEL] [flags]
Inherited flags
| Flag | Type | Default | Description |
|---|---|---|---|
--data-dir | string | ~/.local/share/orchestrator-zero-node | where the node keeps its identity, uv, Python, runtimes and state |
--log-level | string | info | log level: debug, info, warn or error |
See all oz0-node commands and the global flags.