Usage
Aliases
fleets
Commands
Inherited flags
Examples
Subcommand reference
idyl fleet accept-daemonset-terms
Accept the current DaemonSet terms of the subnet a fleet is assigned to.
A fleet accepts its subnet’s DaemonSet terms when it is assigned to the
subnet. When the subnet’s operator later widens the terms, the fleet stays on
the revision it accepted until its owner accepts the new one; narrower terms
apply at once without acceptance. ‘idyl fleet get’ shows the subnet’s current
terms in full, the accounts they name and the per-node ceiling, beside the
copy the fleet accepted while a newer revision awaits acceptance.
—revision is required and must be the subnet’s current revision, so a
fleet never accepts terms that changed after its owner read them.
Usage
Flags
Examples
idyl fleet add-node
Move a node into a fleet in the same subnet.
Fleet membership is recorded on the node, so this sets the node’s fleet. A
node always belongs to exactly one fleet, the one it joined, so adding it to
another fleet moves it there. Both fleets must serve the same subnet: a node
never changes subnet, and serving another subnet means deleting the node and
joining the machine to a fleet in that subnet.
Usage
Flags
Examples
idyl fleet create
Create a fleet in the current account, serving one subnet.
The subnet comes from —subnet, IDYL_SUBNET, or the current context, and one
is required. It is fixed for the life of the fleet: capacity for another
subnet is another fleet. Creating a fleet in a subnet another account owns is
subject to that subnet’s provider admission: an open subnet admits it at once,
an invite subnet admits it if its owner invited this account, and an approval
subnet records a request its owner decides. The fleet’s Attached condition
reports the outcome.
The name is the fleet’s stable handle within the account and is fixed for the
life of the fleet. The 12-digit Fleet ID the platform assigns is what other
commands address the fleet by.
Usage
Flags
Examples
idyl fleet delete
Delete a fleet together with every Node in it.
Each Node of the fleet is deleted the way ‘idyl node delete’ deletes one: by
default it drains first, within the fleet’s drain timeout, and —no-drain
skips the drain for every Node. The fleet’s JoinTokens are revoked and it
refuses new joins from the moment the deletion is accepted.
Deletion is asynchronous: the fleet reads as draining until it has no Nodes,
and is then 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 fleet as the deletion left it.
You will be prompted for confirmation unless the —yes flag is provided.
Usage
Aliases
rm
Flags
Examples
idyl fleet edit
Change how a fleet’s Nodes are brought to new software.
—set-updates automatic has the platform update the fleet’s Nodes to the
release approved for it whenever that release changes; —set-updates paused
stops that, leaving only the updates started with ‘idyl fleet update’.
—set-pin holds the fleet on one stable release version, which the platform
accepts only if that release was approved for the fleet’s subnet. A pin
applies in either mode and never moves a Node to an older release than the
one it runs. —clear-pin removes the pin, so the fleet follows the release
approved for its subnet.
The edit changes only the fleet’s update mode and pin. How many Nodes may be
unavailable at once, the maintenance window and the drain stay as the fleet
has them; where it sets none, the platform’s default applies. A fleet’s name
and subnet are fixed at creation.
Usage
Flags
Examples
idyl fleet events
Show a fleet’s observed history, oldest first.
A fleet’s status says what is true now. Its events say what happened: every
launch attempted, what the cloud said when one was refused, machines replaced
because they never joined, strays terminated, teardown blocked.
Identical consecutive observations are collapsed into one row that counts up,
so a launch retried every few minutes for a day is one line whose count and
last-seen move rather than hundreds of lines.
Use —watch to keep reading. Following resumes from the position each page
ended at, so nothing is read twice and nothing is missed.
Usage
Flags
Examples
idyl fleet get
Get fleet details or list fleets
Usage
Aliases
listls
Flags
idyl fleet list-nodes
List the nodes in a fleet.
Fleet membership is recorded on each node, so this reads the account’s nodes
and selects the ones that name this fleet. The listing is read to its end
before any result is shown, and the summary line reports how many nodes were
examined.
The listing is paged by position, so a node created or removed while the scan
is reading moves rows across page boundaries. An attempt that ends holding
fewer nodes than the account’s own count, or that reaches a page carrying only
nodes it has already read, starts the scan over from the beginning. A
shortfall one attempt establishes stays in force for the rest of the command,
and a later attempt clears it by reading the nodes that were missing rather
than by reporting a smaller count. A listing that comes out that way
on all 3 attempts fails the command, and the failure names how many nodes the
last attempt read alongside the count the account gave for itself, or says the
account gave none.
The account’s count is a check on the scan rather than a guarantee of it.
Removing a node from a position the scan has already passed pulls an unread
node back into that position, and the two counts still agree, so a node can be
absent from a result that passed the check. Reading the listing again opens
that window once more rather than closing it. Running the command again reads
the listing fresh.
NODE CREATED is the date the node itself came into existence. Fleet membership
is a field on the node rather than a record of its own, so the node’s creation
date is the date this listing carries.
Usage
Aliases
ls-nodesget-nodes