Write the system-owner Secret manifest
Synopsis
Applies a Kubernetes Secret containing the authenticated user's email and refresh token to the cluster via kubectl.
The Service Manager Backend reads this secret at runtime for:
- Unattended communication with the developer portal API
- License activation via Cryptlex
Requires prior authentication via "nova login" and a configured kubectl context.
nova bootstrap system-owner [flags]
Options
-h, --help help for system-owner
Options inherited from parent commands
--debug Write diagnostic output to stderr: HTTP requests and responses, external commands, the resolved instance. Known secrets are redacted, but bodies (app environments, kubeconfigs) can still contain some: don't share the output unreviewed (env: NOVA_DEBUG=1)
--dry-run Print manifests to stdout instead of applying via kubectl
--env string (Wandelbots internal) Portal environment for this invocation: prod, stg or dev (default: the environment of the cloud instance, else of the last 'nova login'; env: NOVA_ENV)
--http-proxy string HTTP proxy for deployed workloads (global.proxy.httpProxy); does not affect the CLI's own calls
--https-proxy string HTTPS proxy for deployed workloads (global.proxy.httpsProxy); does not affect the CLI's own calls
--insecure-skip-tls-verify If true, the server's certificate will not be checked for validity (disables TLS verification for all requests)
--instance string Name of the instance to work against for this invocation (overrides the selected instance; env: NOVA_INSTANCE)
--namespace string Target Kubernetes namespace (default "wandelbots")
--no-proxy string Comma-separated NO_PROXY entries (global.proxy.noProxy); does not affect the CLI's own calls
--use-k3s-proxy-env Read HTTP_PROXY/HTTPS_PROXY/NO_PROXY from /etc/systemd/system/k3s.service.env on a cluster node (via a transient pod) instead of passing --http-proxy/--https-proxy/--no-proxy; explicit flags take precedence
SEE ALSO
- nova bootstrap - Bootstrap NOVA on an on-premise IPC