shc hud
shc hud
Section titled “shc hud”open the platform TUI (k9s’s UX over the SHC provider)
Synopsis
Section titled “Synopsis”Open the full-screen platform TUI: k9s’s exact terminal UX
(the : command bar, live tables, / filter, d describe,
l log follow, s shell, Shift-F port-forward, a actions,
e edit, ctrl-n create, x reveal a secret, c copy) over
this platform instead of a Kubernetes cluster (x9s, with the SHC
provider baked in).
It opens on :deployments at the shc ctx tenant, environment
and stack, pinning none of them. An explicit --tenant (a pin),
--environment or --stack, or -t, -e and -s as on every verb, or
the matching $SHC_*, wins.
Every argument is passed through to the embedded provider
(--url, --token, --tenant, --daemon-socket, …; see
shc hud --x9s-serve --help). Config lives under
shc hud [flags]Options
Section titled “Options” -h, --help help for hudOptions 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 - Selfhosted Cloud CLI