EN | JA

Agent-mediated updates

The existing Windows installer jobs update the backend, client and broker through an enrolled agent. Agent self-update also supports Linux and Apple Silicon macOS. Linux backend deployment uses the separate bundle/setup flow; macOS Client deployment integration is deferred. These flows still require working credentials, connectivity and a running agent; offline recovery may require direct host access.

This chapter has one page per component:

Common machinery used by all of them:

Bucket / StreamPurpose
OBJECT_APP_PACKAGESGeneric binary storage (backend, client, NATS server, …). Keyed by <name>/<version>.
OBJECT_SCRIPTSPowerShell script bodies referenced by manifests via script_object. Keyed by <name>/<version>.
OBJECT_AGENT_RELEASESAgent binaries only. Separate from APP_PACKAGES because agent rollout has its own watcher / target_version flow.
agent_config (KV)Layered config — global / per-group / per-PC. target_version lives here.
jobs (KV)Job catalog. Each entry is a manifest the operator can exec.

The CLI surface:

kanade app, kanade script and kanade agent (publish / rollout / current / logs) talk to the backend HTTP API, not to NATS: they need KANADE_AUTH_TOKEN (see kanade login) for an account with the operator role, and no broker token. Publishes and deletes are audited against that account by the backend. Operators who previously relied on the NATS token alone must now export KANADE_AUTH_TOKEN; without it the backend answers 401 / 403. The NATS user pair in the server settings' agent_install section is the agent role's credential, shared by all agents by design, and the backend- generated installers embed it (alongside the token) only when both halves are set. The backend's own credential and the break-glass credential never go in those settings.

kanade agent publish is capped by the backend at 64 MB for the whole upload (a normal agent binary is well under that). app publish additionally downloads the package back from the backend and checks its digest before reporting success.

CommandWhat it does
kanade app publish <name> <file> [--version <version>]Upload to OBJECT_APP_PACKAGES through the backend API.
kanade script publish <name> <version> <file>Upload to OBJECT_SCRIPTS through the backend API.
kanade job create <yaml>Upsert a job manifest into the jobs KV.
kanade exec <job-id> --pcs <pc1>,<pc2>Fire a registered job at a set of PCs.
kanade agent publish <file> [--version <version>]Upload an agent binary through the backend API (must be an official kanade-agent carrying release metadata; the version is read from it and --version, if given, must match — see Agent release admission).
kanade agent rollout <version> --pc | --group | --globalFlip target_version on the chosen scope; agents pick it up via their self-update watcher. Goes through the backend API.
kanade agent currentPrint the global target_version (group / pc overlays are not shown; use kanade config get --group/--pc).
kanade agent logs <pc_id> [--tail <n>]Tail an online agent's log via the backend API.