Skip to main content
Wait for a resource to reach a condition. The —for condition is required. The —timeout flag defaults to 5m. Set —timeout=0s to evaluate the current resource snapshot only and exit without watching for changes. Supported resources and conditions:
  • pod: started, ready, complete, deleted
  • sandbox: started, ready, deleted
  • job: started, complete, deleted
  • deployment: started, ready, deleted
  • replicaset: started, ready, deleted
  • daemonset: ready, deleted
  • hostpodset: ready, deleted
  • namespace: deleted
  • computer: deleted
  • fleet: ready, attached, deleted, phase=<phase>, condition=<name>
  • node: ready, connected, deleted, version=<version>
  • fleet-update: complete
  • fleet-lease: fulfilled, condition=<name>
  • cloud-account: connected, condition=<name>
Workloads are addressed by name within a namespace, and computers by name within a namespace and the subnet they live in; a namespace is addressed by name alone; fleets, fleet updates, fleet leases, and cloud accounts are addressed by the 12-digit ID the platform assigned them, and a node by its node ID. A fleet is ready once its capacity is satisfied and attached once it serves its subnet; phase=<phase> waits for the phase it reports: pending, detached, provisioning, ready, degraded, draining, or terminated. A node is ready once it can run workloads and connected once its control connection is up; version=<version> waits until it runs that idyld release, compared exactly, such as version=0.2.78. A fleet update, which ‘idyl fleet update’ and ‘idyl node update’ start and name by ID, is complete once it has completed; one that was cancelled or failed will not complete, and one that is paused or blocked is still waiting. A fleet or a node whose deletion was accepted will not reach any condition but deleted. A namespace or a computer is released asynchronously after ‘idyl namespace delete’ or ‘idyl computer delete’ accepts the deletion. Waiting for deleted blocks until the platform has finalized the release and the name no longer resolves; while it is terminating the wait reports what still holds it back. A fleet or a node is removed asynchronously after ‘idyl fleet delete’ or ‘idyl node delete’ accepts the deletion: a node drains first unless the deletion skipped it, and a fleet is removed once it has no nodes. Waiting for deleted blocks until the fleet or node no longer resolves. A deleted fleet or node that is removed leaves nothing to print, so with -o json or -o yaml a wait that reaches deleted prints nothing. Fleets, fleet leases, and cloud accounts report conditions — named properties, each with a reason from a closed set. —for=condition=<name> waits on one of them directly, for a property with no shorthand of its own: Attached, Launching, CapacitySatisfied fleet Accepted, Fulfilled fleet-lease Verified cloud-account Exit status says what happened, so a script can tell the three outcomes apart without reading any output. It means the same thing for every resource above: 0 the condition was reached 124 the deadline passed with the condition not yet reached; the resource may still reach it 125 the condition will not be reached — the workload failed or was deleted, a fleet or node is being deleted, a fleet update was cancelled or failed, or capacity reports something that has to change first: the resource’s own spec, the catalog it draws on, the cloud account it provisions into, or a host check the node failed 1 the command could not run: no session, an unknown resource, bad arguments The reason a wait ended is written to standard error whichever way it ended, so the status is what a script reads and the reason is what a person reads. A Supervisor has no name, so it is waited on with ‘idyl supervisor wait —for available|deleted’, which exits under the same contract. Resource aliases match the rest of the CLI:
  • deployment, deployments, deploy
  • replicaset, replicasets, rs
  • daemonset, daemonsets, ds
  • hostpodset, hostpodsets, hps
  • pod, pods
  • job, jobs
  • sandbox, sandboxes
  • namespace, namespaces, ns
  • computer, computers, ws
  • fleet, fleets
  • fleet-update, fleet-updates
  • fleet-lease, fleet-leases, lease, leases
  • cloud-account, cloud-accounts
  • node, nodes

Usage

Commands

Flags

Inherited flags

Examples

Subcommand reference

idyl wait cloud-account

Wait for a cloud-account condition

Usage

Aliases

  • cloud-accounts

Flags

idyl wait computer

Wait for a computer condition

Usage

Aliases

  • computers

Flags

idyl wait daemonset

Wait for a daemonset condition

Usage

Aliases

  • daemonsets
  • ds

Flags

idyl wait deployment

Wait for a deployment condition

Usage

Aliases

  • deployments
  • deploy

Flags

idyl wait fleet

Wait for a fleet condition

Usage

Aliases

  • fleets

Flags

idyl wait fleet-lease

Wait for a fleet-lease condition

Usage

Aliases

  • fleet-leases
  • lease
  • leases

Flags

idyl wait fleet-update

Wait for a fleet-update condition

Usage

Aliases

  • fleet-updates

Flags

idyl wait hostpodset

Wait for a hostpodset condition

Usage

Aliases

  • hostpodsets
  • hps

Flags

idyl wait job

Wait for a job condition

Usage

Aliases

  • jobs

Flags

idyl wait namespace

Wait for a namespace condition

Usage

Aliases

  • namespaces
  • ns

Flags

idyl wait node

Wait for a node condition

Usage

Aliases

  • nodes

Flags

idyl wait pod

Wait for a pod condition

Usage

Aliases

  • pods

Flags

idyl wait replicaset

Wait for a replicaset condition

Usage

Aliases

  • replicasets
  • rs

Flags

idyl wait sandbox

Wait for a sandbox condition

Usage

Aliases

  • sandboxes

Flags