Skip to content
SHC Docs

shc node forget

forget a node

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]
-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 prompt
--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)
  • shc node - manage and inspect cluster nodes