smm install

smm install

Install Calisti

Synopsis

Installs Calisti.

The command automatically applies the resources. It can only dump the applicable resources with the ‘–dump-resources’ option.

The command can install every component at once with the ‘–install-everything’ option.

smm install [flags]

Examples

  # Default install.
  smm install

  # Install Service Mesh Manager into a non-default namespace.
  smm install -n smm-system

Options

      --additional-cp-settings string   A yaml file containing additional settings to be added to the freshly created control plane object.
      --anonymous-auth                  Switch to anonymous mode
      --api-image string                Image for the API
      --cluster-name string             Name of the cluster
  -d, --dump-resources                  Dump resources to stdout instead of applying them
      --enable-ha                       Enable HA mode for smm components (3+ nodes in the destination cluster required for HA functionality)
  -h, --help                            help for install
      --install-cert-manager            Install cert manager (default true)
  -a, --install-everything              Install all required components at once
      --install-sdm                     Install Streaming Data Manager (default false)
      --istio-cr-file string            Filename of a custom Istio CR yaml
      --istio-namespace string          Namespace of Istio sidecar injector (default "istio-system")
      --platform string                 Target Kubernetes platform (may take the values "openshift" or empty for any other)
      --release-name string             Name of the release (default "smm")
      --run-demo                        Install demo application, send load and open up the dashboard
      --web-image string                Image for the frontend

Options inherited from parent commands

      --api-server-endpoint-address string   The publicly accessible address of the k8s api server
      --base-url string                      Custom Service Mesh Manager base URL (uses port forwarding or proxying if empty)
      --cacert string                        The CA to use for verifying Service Mesh Manager's server certificate
      --color                                use colors on non-tty outputs (default true)
      --context string                       name of the kubeconfig context to use
      --controlplane string                  name of the control plane resource to connect to, if not specified, use autodetection
      --formatting.force-color               force color even when non in a terminal
      --http-proxy string                    http proxy to be used for installing SMM components, format: hostname:port (default: empty, no proxy)
      --interactive                          ask questions interactively even if stdin or stdout is non-tty
  -c, --kubeconfig string                    path to the kubeconfig file to use for CLI requests
  -p, --local-port int                       Use this local port for port forwarding / proxying to SMM (when set to 0, a random port will be used) (default -1)
      --no-proxy string                      list of hosts to not to use HTTP proxy for (comma separated list of hostnames and ip subnets)
      --non-interactive                      never ask questions interactively
  -o, --output string                        output format (table|yaml|json) (default "table")
      --persistent-config-file string        Service Mesh Manager persistent config file to use instead of the default at ~/.cisco/smm/
      --resource-wait-timeout duration       The length of time to wait before giving up on waiting for resource conditions to met (default 5m0s)
      --skip-validate-kubeconfig             Skip validating cluster reachability
      --smm-namespace string                 Namespace in which Service Mesh Manager is installed [$SMM_NAMESPACE]
      --token string                         Authentication token to use to communicate with Service Mesh Manager
      --use-portforward                      Use port forwarding instead of proxying to reach Service Mesh Manager
  -v, --verbose                              turn on debug logging

SEE ALSO

• smm - Install and manage Service Mesh Manager