Skip to content
SHC Docs

shc tenant

manage tenants

Manage tenants (the top-level scoping boundary in SHC).

A tenant owns its own deployments, overlay network, and Keycloak realm. Tenants are created on the daemon and surfaced here via the shc tenant subtree.

This is a naming and scoping boundary, not a sandbox for code you do not trust: tenants share a node’s kernel and container daemon, and the network separation is a firewall policy rather than a security boundary.

shc tenant [flags]
-h, --help help for tenant
--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)