NOVA CLI reference 0.5.0 GitHub
  1. nova
  2. nova bootstrap

nova bootstrap service-manager

Write the service-manager HelmChart manifest

Synopsis

Applies a HelmChart custom resource to the cluster via kubectl.

k3s deploys HelmChart CRs via its built-in Helm controller.

By default the latest available release is resolved from the developer portal (use --channel stable|next, or --version to pin a specific version).

nova bootstrap service-manager [flags]

Options

      --channel string        Release channel used to resolve the latest version: stable or next (default "stable")
  -h, --help                  help for service-manager
      --oci-chart string      Chart path within the OCI registry (default "helm/service-manager")
      --oci-registry string   OCI registry for the chart (default "wandelbots.azurecr.io")
      --pull-secret string    Docker registry secret name for chart pulls (default "pull-secret-wandelbots-azurecr-io")
      --version string        Service-manager chart version (default resolves the latest from the portal) (default "x.x.x")

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