shc node forget
shc node forget
Section titled “shc node forget”forget a node
Synopsis
Section titled “Synopsis”Remove a node from the cluster’s registry.
Refuses while deployment rows still name the node (X400017NODDEP): removing it would leave them pointing at a node that no longer exists. Relocate them with shc node drain <node> first: it moves every deployment bound to the node, running or stopped. Clear anything it still leaves behind with shc uninstall <stack>.
--force skips that refusal only. The rows are not evicted or moved: they are left naming the removed node. The quorum floor is never bypassable.
shc node forget <node> [flags]Options
Section titled “Options” -f, --force remove the node even though deployment rows still name it; those rows are left naming a node that is gone (nothing is evicted or moved) -h, --help help for forget -y, --yes skip confirmation promptOptions inherited from parent commands
Section titled “Options inherited from parent commands” --config stringArray extra YAML config file to layer on top of auto-discovered config; repeatable, later files win -d, --debug enable debug mode (default: $SHC_DEBUG) -e, --environment string environment name (default: "prod", or "default" on an estate with no licence and no trial; $SHC_ENVIRONMENT and shc ctx -e override it, and the "master" tenant is always "default") --exclude string comma-separated dotted paths to drop --fields string comma-separated columns/keys to show (and their order) --filter string comma-separated dotted paths to keep (drops everything else) -o, --output string output format: tty|text|json|yaml (default: $SHC_OUTPUT) -s, --stack string stack name (default: $SHC_STACK) -t, --tenant string tenant name (default: $SHC_TENANT) -v, --verbose verbose output (default: $SHC_VERBOSE)SEE ALSO
Section titled “SEE ALSO”- shc node - manage and inspect cluster nodes
shc@docs:~$