Usage
Aliases
supervisors
Commands
Inherited flags
Subcommand reference
idyl supervisor create
Create the Supervisor of the resolved Namespace in the resolved subnet.
By default the Supervisor targets every eligible Node of the subnet; —fleet
restricts it to the Nodes of one fleet in the subnet. The placement is fixed
at creation: a Supervisor on a different fleet, or on none, is a new
Supervisor, created after this one is deleted. —cpu and —memory set what
each supervisor Pod is given; the platform default applies to either one left
out. —keep-warm keeps one host ready for the Namespace’s Computers at all
times, so a dormant Computer wakes without waiting for a host to start; that
host reserves its CPU and memory on a Node permanently, whether or not any
Computer runs. ‘idyl supervisor edit’ changes all three later.
A Namespace has at most one Supervisor in each subnet, so creating one where
the Namespace already has one is refused. Creation needs a subnet able to
accept new work. With -o json or -o yaml the command prints the Supervisor as
the platform recorded it.
Usage
Flags
Examples
idyl supervisor delete
Delete the Supervisor of the resolved Namespace in the resolved subnet.
Deletion is asynchronous. The platform accepts it, reports the Supervisor as
deleting, releases its Nodes and the DaemonSet it controls, and removes it on
its own; once it is gone the Namespace has no Supervisor in the subnet and one
may be created again. While it is deleting the Supervisor still reads.
—wait blocks until the Supervisor is gone and exits the way ‘idyl wait’ does:
0 gone, 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 platform’s answer to the delete, or with —wait the wait’s result.
You will be prompted for confirmation unless the —yes flag is provided.
Usage
Aliases
rm
Flags
Examples
idyl supervisor edit
Change the CPU and memory each supervisor Pod of the resolved Namespace’s
Supervisor is given, or whether it keeps a warm host. They are the only part of
a Supervisor that changes after creation; a flag left out keeps its current
value.
—keep-warm=true keeps one host ready for the Namespace’s Computers at all
times, so a dormant Computer wakes without waiting for a host to start; that
host reserves its CPU and memory on a Node permanently, whether or not any
Computer runs. —keep-warm=false stops keeping it: the host is then released
like any other host once it has been empty for the platform’s retention. The
WarmHost condition in ‘idyl supervisor get’ reports whether the host is held.
The placement cannot change. A Supervisor restricted to a different fleet, or
to none, is a new Supervisor: delete this one and create it with the placement
it needs.
With -o json or -o yaml the command prints the Supervisor after the change.
Usage
Flags
Examples
idyl supervisor get
Show the Supervisor of the resolved Namespace in the resolved subnet: its
phase, the supervisor version, the DaemonSet it controls, its conditions, the
state of every Node it targets, and the HostPodSets its Nodes serve.
A Node is covered when its supervisor Pod is ready, has registered and
reconciled the Node, and is not draining; only a covered Node may hold the
Namespace’s units. REASON says why a Node is not covered. Each HostPodSet
shows whom it serves, its desired and ready hosts, and the CPU and memory its
ready hosts hold free.
With -o json or -o yaml the command prints the Supervisor as the platform
reports it.
Usage
Flags
Examples
idyl supervisor list
List the Supervisors in the resolved subnet, across every Namespace you may
list in the account. Each Namespace has at most one Supervisor in a subnet, so
the listing names each one by its Namespace.
Usage
Aliases
ls
Flags
Examples
idyl supervisor wait
Wait for the Supervisor of the resolved Namespace in the resolved subnet to
reach a condition.
- available: the Supervisor reports its Available condition True: at least one targeted Node is covered, registered, and reconciled, and nothing blocks the Supervisor, such as a subnet that does not admit its DaemonSet or refuses a workload it needs. Until then the wait reports the condition’s reason. A Supervisor that targets no Node is never available, and one that is deleting will not become available.
- deleted: the Supervisor no longer exists.