Skip to main content
Manage Nodes through the API. Nodes are installed and joined with idyld on each machine. These commands manage any number of Nodes remotely and never act on the machine running idyl.

Usage

Aliases

  • nodes

Commands

Inherited flags

Examples

Subcommand reference

idyl node delete

Delete a Node from the account. By default the Node drains first: it takes no new Pods, and its Pods stop gracefully and are replaced elsewhere in its Fleet, within the Fleet’s drain timeout. At that timeout the deletion goes ahead whether or not every Pod has stopped. Then the Node’s credential is refused and the Node is removed. —no-drain skips the drain and deletes the Node at once. A Node that is not connected cannot drain and is deleted at once either way. The machine removes its Node identity when it learns of the deletion; the installed software stays. Joining the machine again with a new JoinToken makes a new Node with a new ID. Deletion is asynchronous: the Node reads as deleting until it is removed. —wait blocks until it is removed and exits the way ‘idyl wait’ does: 0 removed, 124 when —timeout passes first. Without it the command returns as soon as the deletion is accepted. With -o json or -o yaml the command prints the Node as the deletion left it. You will be prompted for confirmation unless the —yes flag is provided.

Usage

Aliases

  • rm

Flags

Examples

idyl node edit

Set or clear a provider node’s account-owned display name. The argument is the canonical node ID and is required. Display names are presentation labels only and are never resolved as identifiers.

Usage

Flags

Examples

idyl node get

List the account’s Nodes, or show one Node in detail. With no argument, lists every current Node in the account, connected or not, across all of its Fleets and Subnets. A Node whose deletion has finished is no longer listed. With a Node ID, shows that Node: its release support, phase, version, conditions, the latest report of its host checks with the fix for each failing check, its capacity, and its lifecycle. HOST summarizes the Node’s HostReady condition: ready while no host check fails, failing with the first failing check’s name while one does, unknown until the Node has reported its checks, and a dash when the platform reports no HostReady condition. CONNECTED is how long the current connection has been up, and a dash while the Node is not connected. -o wide adds SUBNET, CPU, MEMORY, and GPU to the listing; the detail view always shows them. -o json and -o yaml print the platform’s response.

Usage

Aliases

  • list
  • ls

Flags

Examples

idyl node support

Read the Network’s Standard Support intervals, tested release paths, and upgrade notes. This command does not start an update or change support policy.

Usage

Flags

idyl node update

Preview an eligible release for exactly one Node, show its exact sequence and manifest digest, capacity impact, safety strategy, and blockers, then ask for confirmation before creating the FleetUpdate that selects that fixed Node.

Usage

Flags

Examples

idyl node updates

Show the read-only software update dashboard for one Node, including its current release, eligible targets, Fleet budget, blockers, active FleetUpdate, and per-Node progress.

Usage

Flags

Examples