oz0 server dist channel
Show the release channel the cluster follows: stable, preview (release candidates, and the stable releases too) or lts-<major>.<minor>, one long-term support line.
For: Operators and developers looking up a command.
Show the release channel the cluster follows: stable, preview (release candidates, and the stable releases too) or lts-<major>.<minor>, one long-term support line. With CHANNEL, move the cluster to it: nodes then take only releases of that channel, and management upgrades nodes only to a release the edge serves on it. A move needs --reason and is recorded in the audit log. It runs on a server's machine and needs the database (--db-file, OZ0_DB or --dev), not the master key.
Then mirror a release of the channel into each edge's dist folder with server dist pull.
Usage
oz0 server dist channel [CHANNEL] [flags]
Flags
| Flag | Type | Default | Description |
|---|---|---|---|
--data-dir | string | ~/.local/share/orchestrator-zero | server data directory |
--db-file | file | a file (- for stdin) holding the PostgreSQL URL of the management database, such as postgres://oz0:PASSWORD@db:5432/oz0 (or set OZ0_DB); the URL can carry a password, so it never goes on the command line | |
--dev | bool | a dev server's data directory (--data-dir) instead of a cluster's database | |
--reason | string | why the cluster moves, for the audit log (required to move it) |
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.