An Exoscale node
This page has not been walked: no SHC test account exists on Exoscale. Its command lines are what the CLI takes; its output lines are left open.
Exoscale has zones and no regions. The exoscale connection lights DNS
only, and Exoscale DNS is a paid add-on on the account, so most estates
on Exoscale point a cloudflare connection at a zone they own instead. A
deployment on an Exoscale node keeps its data on the node’s disk.
Write the API key pair on home01 as ~/exoscale.json.
{"api_key": "<api key>", "api_secret": "<api secret>"}$ chmod 600 ~/exoscale.jsonCreate one instance: Debian 13, zone de-fra-1, named after the node,
in a security group that allows the cluster ports between it and the
learn nodes. Install SHC on it. Call the node exo01.
The join asks home01 for its token over ssh, so give root on exo01 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 exo01 --cloud exoscale --location de-fra-1...$ shc node ls...$ shc connection connect exoscale --cred zone=de-fra-1 --value-file ~/exoscale.json...$ shc connection show exoscale...$ shc install ~/learn/nginx -s exoweb --where node=exo01 --expose 18086=nginx:80...$ curl -s http://localhost:18086/...$ shc uninstall exoweb -y...$ shc node leave...$ shc node ls...$ shc connection rm exoscale --yes...Delete the instance 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: A Hostinger node.