An UpCloud node
This page has not been walked: no SHC test account exists on UpCloud. Its command lines are what the CLI takes; its output lines are left open.
The upcloud connection takes an API token and a zone. It lights a load
balancer and block storage; UpCloud has no DNS API, so DNS comes from
another connection. UpCloud nodes are detected: a server records
upcloud and its zone on its own.
Put the token on home01 as ~/upcloud.token.
$ chmod 600 ~/upcloud.tokenCreate one server: Debian 13, zone fi-hel1, named after the node, with
a firewall that allows the cluster ports between it and the learn nodes.
Install SHC on it. Call the node up01 and join it without saying where
it is.
The join asks home01 for its token over ssh, so give root on up01 the learn nodes’ names and a key home01 accepts, as the learn nodes have.
$ ssh home01 shc node token --fields token -o text | shc node join - --name up01...$ shc node ls...$ shc connection connect upcloud --cred zone=fi-hel1 --cred token=- --value-file ~/upcloud.token...$ shc connection show upcloud...$ shc install notes -s updb --where node=up01 --storage upcloud...$ shc volume ls...$ shc uninstall updb -y...$ shc volume ls...$ shc node leave...$ shc node ls...$ shc connection rm upcloud --yes...Delete the server in the hub.
This page leaves the cluster as the runtimes ladder left it: the learn nodes, with no cloud node and no connection.
Next: A Vultr node.