Underneath the label and the location
Read this right after A label and a location. Every command here reads; none changes the cluster.
Nobody typed a location label. home01 was initialized with --cloud learn --location home, and SHC derives labels from that:
$ shc label ls -vLABEL SOURCE NODES READY RESERVED CONSTRAINTS DEPLOYMENTS GRANTED MEMBERS BACKUP-REPO DESCRIPTION CREATEDcloud=learn derived 1 1 no 0 0 - home01 - - 2026-10-08 15:28:56control-plane system 1 1 no 0 0 - home01 - - 2026-10-08 15:28:56location=learn derived 1 1 no 0 0 - home01 - - 2026-10-08 15:28:56location=learn/home derived 1 1 no 1 1 - home01 - - 2026-10-08 15:28:56...location=learn/home has one member, home01, and one constraint: the rule set
on placed. A rule names a label path, so location=learn would match every
node in cloud learn, and a node that joins with --location far would get
location=learn/far and sit outside this rule.
The deployment’s label tier=learn is not a node label. It describes the
deployment, and shc ls --where selects by it. The rule and what it leaves:
$ shc status -s placedlast polled 2026-11-04 18:26:01 UTCNODE STATE CPU% MEM% DISK% LOADhome01 healthy 78.2 22.2 8.7 1.78
all 68 queues green
TENANT STACK ENVIRONMENT STATE SERVICES NODE LABELSprod placed prod healthy 1/1 home01 app=notes environment=prod stack=placed tenant=prod tier=learn
TENANT STACK ENVIRONMENT REPLICA NODE STATEprod placed prod postgres-r0 home01 ready
runs on home01; no other node to move to
1 node, 1 deploymentCONSTRAINTS is the rule as set, with the nodes it removes and keeps.
DERIVED CONSTRAINTS are SHC’s own: only ready nodes take new work.
eligible is what is left.
Next: A backup and an export.