Skip to content
SHC Docs

A DigitalOcean node

This page has not been walked: no SHC test account exists on DigitalOcean. Its command lines are what the CLI takes; its output lines are left open.

One DigitalOcean API token serves DNS, the load balancer and block volumes. The load balancer and the volumes are created in the connection’s region, so a node’s location is its region slug.

Put the token on home01 as ~/digitalocean.token.

home01
$ chmod 600 ~/digitalocean.token

Create one droplet: Debian 13, region nyc3, named after the node, with a cloud firewall that allows the cluster ports between it and the learn nodes. Install SHC on it. Call the node do01.

The join asks home01 for its token over ssh, so give root on do01 the learn nodes’ names and a key home01 accepts, as the learn nodes have.

do01
$ ssh home01 shc node token --fields token -o text | shc node join - --name do01 --cloud digitalocean --location nyc3
...
home01
$ shc node ls
...
$ shc connection connect digitalocean --cred region=nyc3 --cred token=- --value-file ~/digitalocean.token
...
$ shc connection show digitalocean
...
$ shc install notes -s dodb --where node=do01 --storage digitalocean
...
$ shc volume ls
...
$ shc volume snapshot pgdata -s dodb
...
$ shc uninstall dodb -y
...
$ shc volume ls
...
do01
$ shc node leave
...
home01
$ shc node ls
...
$ shc connection rm digitalocean --yes
...

Destroy the droplet and the snapshot in the console.

This page leaves the cluster as the runtimes ladder left it: the learn nodes, with no cloud node and no connection.

Next: An Exoscale node.