Nodes
A node is a machine that runs containers. The Nodes page lists them with their identity, capacity and health, alongside the node invites that let new machines connect themselves.
Tenant and global nodes
Section titled “Tenant and global nodes”Tenant nodes belong to your tenant. Global nodes are shared across tenants by a superadmin; they appear in your list, and you can enable them for your tenant, but the object itself is not yours to edit.
Adding a node
Section titled “Adding a node”The normal route is an invitation, not direct registration: the machine connects outward and enrols itself, so it does not need to be reachable from the internet.
- Connect new node creates an invite with a label, a validity period and a maximum number of uses.
- Run the command it gives you on the target machine.
- The node appears in the list and reports its GPUs.
- Link it to the queues that should schedule onto it.
A max uses above one lets the same invite enrol several machines - useful for a batch of identical workstations, and worth avoiding otherwise.
Node health
Section titled “Node health”Online means the node currently holds its tunnel to the central server. Offline nodes take no jobs, and their queues have nothing to schedule onto.
A node going offline is not necessarily a fault - many nodes are workstations that are switched off overnight. It does mean users will see “This queue has no node that can run a job right now” until it returns.
Enable and disable
Section titled “Enable and disable”The enable toggle takes a node out of scheduling without removing it. Prefer it to deletion for maintenance: deletion means the machine has to re-enrol with a new invite.
Deleting
Section titled “Deleting”Deleting a node removes it from the tenant. Jobs’ history survives; the machine must enrol again from a fresh invite to come back.