Skip to content
SHC Docs

An Azure node

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

The azure connection is a service principal plus the subscription and resource group it works in. One connection lights Azure DNS, the Standard load balancer and managed disks.

Write the five fields on home01 as ~/azure.json. The client secret is the secret; the ids ride with it.

{"subscription_id": "<subscription id>", "resource_group": "<resource group>", "tenant_id": "<tenant id>", "client_id": "<client id>", "client_secret": "<client secret>"}
home01
$ chmod 600 ~/azure.json

Create one virtual machine in that resource group: Debian 13, region eastus, size Standard_D2s_v4, named after the node, with a network security group that allows the cluster ports between it and the learn nodes. Install SHC on it. Call the node az01.

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

az01
$ ssh home01 shc node token --fields token -o text | shc node join - --name az01 --cloud azure --location eastus
...
home01
$ shc node ls
...
$ shc connection connect azure --cred region=eastus --value-file ~/azure.json
...
$ shc connection show azure
...
$ shc install notes -s azdb --where node=az01 --storage azure
...
$ shc volume ls
...
$ shc uninstall azdb -y
...
$ shc volume ls
...
az01
$ shc node leave
...
home01
$ shc node ls
...
$ shc connection rm azure --yes
...

Delete the virtual machine in the portal.

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

Next: A DigitalOcean node.