Skip to content
SHC Docs

A Scaleway node

Not every cloud connection sells the same things. The scaleway connection lights DNS only: no load balancer and no block volumes, so a deployment on a Scaleway node keeps its data on the node’s disk.

Put the Scaleway secret key on home01 as ~/scaleway.key.

home01
$ chmod 600 ~/scaleway.key

In the Scaleway console create one instance: Debian 13, zone fr-par-1 of region fr-par. Install SHC on it and allow the cluster ports between it and the learn nodes. Call the node scw01.

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

scw01
$ ssh home01 shc node token --fields token -o text | shc node join - --name scw01 --cloud scaleway --location fr-par-1
✔ joined cluster as node "scw01" at 78.232.56.75
home01
$ shc node ls
NAME STATE CONDITION AVAIL CLOUD LOCATION ROOM BUILD LEADER VOTER
home01 healthy ready active learn learn/home ok 0.1.0 yes yes
scw01 healthy ready active scaleway scaleway/fr-par-1 ok 0.1.0 no no
$ shc connection connect scaleway --cred secret_key=- --value-file ~/scaleway.key
✔ connected connection "scaleway", providers scaleway.dns
$ shc connection show scaleway
NAME TYPE TENANT SCOPE REGION ENDPOINT DNS PROVIDERS ID CREATED UPDATED
scaleway scaleway prod tenant - - public dns 80c289c0-e2b3-4896-891a-027c21a7d328 2026-10-09T22:11:23Z 2026-10-09T22:11:23Z
mint: -
┌─ fields ────────────────────────────────┐
│ FIELD SECRET STATUS VALUE │
│ secret_key true set - │
└─────────────────────────────────────────┘

The connection shows one provider, dns. Scaleway DNS answers only for a domain Scaleway hosts, so a zone is added only when you have one there. Install the nginx directory onto scw01: with no volume provider the install asks for none.

home01
$ shc install ~/learn/nginx -s scwweb --where node=scw01 --expose 18085=nginx:80
installing deployment "scwweb"
[scwweb] Healthy 1/1
✔ nginx healthy
✔ installed deployment "scwweb"
exposure: lan
$ shc volume ls
no block volumes in tenant "prod"
scw01
$ curl -s http://localhost:18085/
<!doctype html>
<title>hello</title>
<p>Hello from SHC.</p>
home01
$ shc uninstall scwweb -y
uninstalling deployment "scwweb"
[scwweb] Complete 6/6
✔ remove from scw01
✔ take the safety backup
✔ leave every node's service VIP table
✔ tear down
✔ stop the replicas on scw01
✔ remove the copy on home01
✔ uninstalled deployment "scwweb"

The system ingress keeps a traefik replica on every node, so a node that still hosts one refuses to leave with X409025LVDEPS: drain it first, from any node, and the cluster moves what it hosts. Then the node leaves from itself.

home01
$ shc node drain scw01 --yes
scw01 is a docker-runtime host.
- nothing relocates: traefik runs on every node, so its replica here stops
✔ drained node "scw01"
scw01
$ shc node leave
...
home01
$ shc node ls
NAME STATE CONDITION AVAIL CLOUD LOCATION ROOM BUILD LEADER VOTER
home01 healthy ready active learn learn/home ok 0.1.0 yes yes
$ shc connection rm scaleway --yes
✔ removed connection "scaleway"

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 Google Cloud node.