Skip to content

Compute nodes

Compute nodes represent servers. You place one on the canvas, pick a provider and a size, wire it to networks and IPs, and CrossXCloud creates it on Apply.

Drag a compute node from the resource palette onto the canvas. The inspector opens for it.

Choose provider, location, and server type

Section titled “Choose provider, location, and server type”

A compute node always belongs to a connected provider. The inspector’s dropdowns are filled from the real provider catalog, so the server types, images, and locations you see are what that account can actually create.

For a Hetzner example, you might name a node web-01, set its location to fsn1, and set its server type to cx32.

For a Google Cloud example, you set a zone and a machine type from the catalog.

These three fields (provider, placement, and sizing) are the core of what makes a compute node unique. They are immutable after Apply for some providers. Changing an immutable field later does not silently update the resource. CrossXCloud plans a delete and a create instead. See Reconciliation for why.

The image field picks what the server boots from. The dropdown comes from the provider catalog, so for Hetzner you might pick ubuntu-22.04.

The inspector has a toggle to enable a public IP for the compute node. Turn it on and a primary IP companion node appears next to the compute node automatically.

The primary IP is a canvas artifact, not a separate resource you manage. It has no fields. It shows the live public IP address once the compute node exists. It is created with the compute node and deleted with it.

If you want a static, independently-managed public IP that survives the compute node, use a floating IP instead. See Networking.

Drag from a private network node onto the compute node to put the compute node in that network. Drag from a floating IP node onto the compute node to assign the IP. Both of these are edges, not fields. See Networking and The canvas model.

The compute node has a bootstrap field for a startup script the server runs on first boot. Use it to configure the machine without SSH-ing in.

  • Networking covers private networks and IPs in detail.
  • Plan and Apply covers what happens when you apply the compute node.
  • Node types lists every field on the compute node.