Skip to content
SHC Docs

Read a deployment's constraints

Run shc constraint explain to see what determines the deployment’s location. shc status wiki includes the same constraint sections alongside health.

CONSTRAINTS lists the where and prefer selectors someone set, with their scope and reason. A where removes nodes; a prefer ranks matches without removing the others. Cluster and tenant constraints still apply when a deployment has its own selector. A label alone changes nothing.

DERIVED CONSTRAINTS names the facts SHC reads from the deployment and its nodes. A limit cannot be crossed: the runtime must match, the node must be ready and it must have enough capacity. Reserved values require a selector that names them. An anchor records where data lives, such as a volume’s reach or a shared volume that keeps services on one node. Crossing an anchor needs a relocation that carries the data.

Each row says which nodes it removes or ranks and which remain. The eligible set follows the rows. RELOCATION considers other nodes that satisfy the limits and lists the anchors each move would cross. A volume outside the candidate’s reach must be copied with the move. An unreachable store refuses that candidate. With no candidates, the reason names the constraint that leaves no alternative.

A not spread line names a member of a group that is on a node already holding another member, and says what left it there: the rules that removed every node without one, the resource those nodes lack, repeated start failures that rank them last, that every node already holds one, or a stated spread whose skew allows it. Members prefer separate nodes ahead of any prefer and ahead of the score, so the line never names either. A member that was bound there before says it is kept: an update does not move a bound member.

The suggested shc update wiki -e prod --where 'node=<candidate>' command uses the existing move path. Explain only reads the snapshot; it neither moves data nor reserves capacity. Recheck before running the command, using the same tenant context.

If explain fails, status still returns health and prints one warning on stderr.