A Vultr node
This page has not been walked: no SHC test account exists on Vultr. Its command lines are what the CLI takes; its output lines are left open.
One Vultr API key serves DNS, the load balancer and block storage. The load balancer and the volumes are created in the connection’s region, so a node’s location is its region code.
Put the API key on home01 as ~/vultr.key.
$ chmod 600 ~/vultr.keyCreate one instance: Debian 13, region ewr, named after the node, with
a firewall group that allows the cluster ports between it and the learn
nodes. Install SHC on it. Call the node vu01.
The join asks home01 for its token over ssh, so give root on vu01 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 vu01 --cloud vultr --location ewr...$ shc node ls...$ shc connection connect vultr --cred region=ewr --cred api_key=- --value-file ~/vultr.key...$ shc connection show vultr...$ shc install notes -s vudb --where node=vu01 --storage vultr...$ shc volume ls...$ shc volume snapshot pgdata -s vudb...$ shc uninstall vudb -y...$ shc volume ls...$ shc node leave...$ shc node ls...$ shc connection rm vultr --yes...Destroy the instance and the snapshot in the portal. This is the last
page of the runtimes and clouds ladder: the cluster is back to home01,
pod01 and inc01, with web, podweb and incweb running on three engines.