Skip to main content
Reference material for UpCloud clusters.

Cluster Configuration Options

The fields of POST /api/v1/clusters/upcloud. The portal’s create form sets most of them; see Create a Cluster.

UpCloud Datacenter Zones

UpCloud Server Plans

Available plans may vary by zone. Check the UpCloud pricing page for the latest offerings.

Node Group API Reference

Node Actions API

See Restart a node and Bastion for how to use them.

Disabled k3s Components API

The k3s_disabled_components list set at create can grow on a running k3s cluster. The body is the complete list and has to contain every entry already stored; an unknown or repeated entry is a 422 validation error pointing at the entry. applies answers: “The platform’s maintenance read lane compares each control plane’s k3s server config against this list within about five minutes and flags the ones missing an entry; the reconcile lane then patches the config and restarts k3s on one control plane at a time, in the cluster’s k8s update chain. Control planes already carrying every entry are not touched. The list only grows: re-enabling a bundled component is not supported yet, so a change that removes a stored entry is refused, and so is any change while a node update, version upgrade or node restart is still in progress on the cluster.” The refusals answer 409 with the detail shown:

Architecture

The managed NAT gateway on the router carries all node egress; the bastion is an SSH jump host only. On a multi-zone cluster each additional zone gets its own router, private network and NAT gateway, and a WireGuard mesh (wg0) joins every node over the account-wide utility network. See What Ankra created in your account.