NOVA CLI reference 0.5.0 GitHub
  1. nova

nova bootstrap

Bootstrap NOVA on an on-premise IPC

Synopsis

Bootstrap a NOVA installation on an on-premise IPC.

Prerequisites:

  • Run "nova login" first to authenticate with the developer portal.
  • kubectl must be configured to access the target cluster e.g. "kubectl config use-context" or "export KUBECONFIG=path/to/config"

The bootstrap process:

  1. Creates the target namespace (nova bootstrap namespace)
  2. Deploys Ember Stack Reflector for cross-namespace secret mirroring (nova bootstrap reflector)
  3. Applies pull secrets from the developer portal (nova bootstrap pull-secrets)
  4. Applies the service-manager HelmChart CR (nova bootstrap service-manager)
  5. Applies the system-owner Secret (nova bootstrap system-owner)

All manifests are applied to the cluster via "kubectl apply".

Use --dry-run to print manifests to stdout instead of applying them. Use "nova bootstrap all" to run all steps in sequence.

nova bootstrap [flags]

Examples

 # Point kubectl to the target cluster context
 export KUBECONFIG=~/.kube/gpu-workstation

 # Login to the developer portal
 nova login

 # Bootstrap NOVA
 nova bootstrap all

# If running behind some proxy that performs SSL inspection, 
# set proxy config and inject the proxy CA certs.
# Make sure cluster internal and local addresses are included in the no-proxy list.
# 
# You might want to check k3s settings at "/etc/systemd/system/k3s.service.env" and use these.
nova bootstrap all \
 --use-k3s-proxy-env \
 --ca-certificates cert.pem

# To explicitly set proxy config and inject the proxy CA certs.
# Make sure cluster internal and local addresses are included in the no-proxy list.
# 
# You might want to check k3s settings at "/etc/systemd/system/k3s.service.env" and use these.
nova bootstrap all \
 --http-proxy http://192.168.56.1:8080 \
 --https-proxy http://192.168.56.1:8080 \
 --no-proxy localhost,127.0.0.0/8,::1,0.0.0.0,10.0.0.0/8,172.16.0.0/12,192.168.0.0/16,192.0.2.1,.svc,.cluster.local,.cluster.local. \
 --ca-certificates cert.pem

Options

      --dry-run              Print manifests to stdout instead of applying via kubectl
  -h, --help                 help for bootstrap
      --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
      --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

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)
      --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)
      --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)

SEE ALSO