This is the multi-page printable view of this section.
Click here to print.
Return to the regular view of this page.
Command reference
The following commands are available in the smm
command-line tool. If you want to uninstall Service Mesh Manager, see Cleanup and uninstall.
Cleanup and Uninstall
To remove the demo application, Service Mesh Manager, Istio, and any other components from your cluster, run the following command. It takes care of removing these components in the correct order.
To delete the Service Mesh Manager operator, run:
$ helm del --purge smm-operator
1 - smm
smm
Install and manage Service Mesh Manager
Options
--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
-h, --help help for smm
--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 activate - Activate local Service Mesh Manager installation by setting up registry access, overwriting the current configuration.
- smm activate-ecr - Activate local Service Mesh Manager installation by setting up registry access, overwriting the current configuration.
- smm analyze - Analyze Service Mesh Manager and Istio configuration
- smm cert-manager - Install and manage cert-manager
- smm clouddoor - Install and manage ASG clouddoor gateway
- smm config - View and manage persistent configuration
- smm dashboard - Open the Service Mesh Manager dashboard in a web browser
- smm demoapp - Install and manage demo application
- smm graph - Show graph
- smm install - Install Service Mesh Manager
- smm istio - Install and manage Istio
- smm license - Manage license
- smm login - Log in to Service Mesh Manager
- smm operator - Install and manage Service Mesh Manager operator
- smm registry - Manage private registry access for Service Mesh Manager
- smm sidecar-proxy - Manage sidecar-proxy related configurations
- smm tap - Tap into HTTP/GRPC mesh traffic
- smm uninstall - Uninstall Service Mesh Manager
- smm version - Print the client and api version information
2 - smm activate
smm activate
Activate local Service Mesh Manager installation by setting up registry access, overwriting the current configuration.
Options
-h, --help help for activate
--host string Host of the registry to be used for fetching smm images [default: SMM_REGISTRY_HOST environment variable's value]
--password string Password to use for authenticating to SMM docker registry [default: SMM_REGISTRY_PASSWORD environment variable's value]
--prefix string Path prefix of the registry to be used for fetching smm images [default: SMM_REGISTRY_PREFIX environment variable's value]
--user string Username to use for authenticating to SMM docker registry [default: SMM_REGISTRY_USER environment variable's value]
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
3 - smm activate-ecr
smm activate-ecr
Activate local Service Mesh Manager installation by setting up registry access, overwriting the current configuration.
Options
-h, --help help for activate-ecr
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
4 - smm analyze
smm analyze
Analyze Service Mesh Manager and Istio configuration
Options
-h, --help help for analyze
--namespace string Filter validation results by namespace
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
5 - smm cert-manager
smm cert-manager
Install and manage cert-manager
Options
-h, --help help for cert-manager
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
6 - smm cert-manager install
smm cert-manager install
Install cert-manager
Synopsis
Installs cert-manager.
The command automatically applies the resources.
It can only dump the applicable resources with the ‘–dump-resources’ option.
smm cert-manager install [flags]
Examples
# Install to the cert-manager namespace. This command will fail if cert-manager is already installed from a different source.
smm cert-manager install
Options
-d, --dump-resources Dump resources to stdout instead of applying them
-h, --help help for install
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
7 - smm cert-manager uninstall
smm cert-manager uninstall
Output or delete Kubernetes resources to uninstall cert-manager
Synopsis
Output or delete Kubernetes resources to uninstall cert-manager.
The command automatically removes the resources.
It can only dump the removable resources with the ‘–dump-resources’ option.
smm cert-manager uninstall [flags]
Examples
# Default uninstall.
smm cert-manager uninstall
# Uninstall cert-manager from a non-default namespace.
smm cert-manager uninstall --cert-manager-namespace smm-system
Options
-d, --dump-resources Dump resources to stdout instead of applying them
--force Force uninstalling cert-manager
-h, --help help for uninstall
--skip Skip uninstalling cert-manager
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
8 - smm clouddoor
smm clouddoor
Install and manage ASG clouddoor gateway
Options
--gateway-namespace string Namespace for ASG clouddoor gateway operator (default "asg-system")
-h, --help help for clouddoor
--istio-revision string Istio control plane revision (format: [istio-resource-name].[namespace])
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
9 - smm clouddoor install
smm clouddoor install
Install ASG clouddoor gateway
Synopsis
Installs ASG clouddoor gateway.
The command automatically applies the resources.
It can only dump the applicable resources with the ‘–dump-resources’ option.
smm clouddoor install [flags]
Examples
# Default install.
smm clouddoor install
# Install gateway into a non-default namespace.
smm clouddoor install -n smm-system
Options
-d, --dump-resources Dump resources to stdout instead of applying them
-s, --enabled-services strings Enabled services of the gateway operator
-h, --help help for install
--no-gateway Disable the creation of the mesh gateway
-r, --replicas uint Replica count of the deployments (only used if HPA is disabled) (default 1)
--requests-cpu uint The gateway operator pods' requested cpu shares in millicores (default 100)
--requests-memory uint The gateway operator pods' requested memory in megabytes (default 64)
--strict-limits Set the gateway operator pods' limits to match the requests, useful for performance testing
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
--gateway-namespace string Namespace for ASG clouddoor gateway operator (default "asg-system")
--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
--istio-revision string Istio control plane revision (format: [istio-resource-name].[namespace])
-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
10 - smm clouddoor uninstall
smm clouddoor uninstall
Output or delete Kubernetes resources to uninstall ASG gateway
Synopsis
Output or delete Kubernetes resources to uninstall ASG gateway.
The command automatically removes the resources.
It can only dump the removable resources with the ‘–dump-resources’ option.
smm clouddoor uninstall [flags]
Examples
# Default uninstall.
smm clouddoor uninstall
# Uninstall ASG gateway from a non-default namespace.
smm clouddoor uninstall -n custom-clouddoor-ns
Options
-d, --dump-resources Dump resources to stdout instead of applying them
-h, --help help for uninstall
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
--gateway-namespace string Namespace for ASG clouddoor gateway operator (default "asg-system")
--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
--istio-revision string Istio control plane revision (format: [istio-resource-name].[namespace])
-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
11 - smm config
smm config
View and manage persistent configuration
Options
-h, --help help for config
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
12 - smm config delete
smm config delete
Delete persistent configuration
smm config delete [flags]
Options
-h, --help help for delete
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 config - View and manage persistent configuration
13 - smm config edit
smm config edit
Edit persistent configuration
Options
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 config - View and manage persistent configuration
14 - smm config view
smm config view
View persistent configuration
Options
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 config - View and manage persistent configuration
15 - smm dashboard
smm dashboard
Open the Service Mesh Manager dashboard in a web browser
Options
-h, --help help for dashboard
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
16 - smm demoapp
smm demoapp
Install and manage demo application
Options
--demo-namespace string Namespace for demo application (default "smm-demo")
-h, --help help for demoapp
--istio-revision string Istio control plane revision (format: [istio-resource-name].[namespace])
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
17 - smm demoapp install
smm demoapp install
Install demo application
Synopsis
Installs demo application.
The command automatically applies the resources.
It can only dump the applicable resources with the ‘–dump-resources’ option.
smm demoapp install [flags]
Examples
# Default install.
smm demoapp install
# Install demo application into a non-default namespace.
smm demoapp install -n smm-system
Options
--disable-autoscaling Disable HPA based autoscaling of the demo application's deployments
--disable-load Do not start the load generator
-d, --dump-resources Dump resources to stdout instead of applying them
-s, --enabled-services strings Enabled services of the demo app
-h, --help help for install
--peer The destination cluster is a peer in a multi-cluster mesh
-r, --replicas uint Replica count of the deployments (only used if HPA is disabled) (default 1)
--requests-cpu uint The demoapp pods' requested cpu shares in millicores (default 40)
--requests-memory uint The demoapp pods' requested memory in megabytes (default 64)
--strict-limits Set the demoapp pods' limits to match the requests, useful for performance testing
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
--demo-namespace string Namespace for demo application (default "smm-demo")
--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
--istio-revision string Istio control plane revision (format: [istio-resource-name].[namespace])
-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
18 - smm demoapp load
smm demoapp load
Start sending load to demo application
Options
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
--demo-namespace string Namespace for demo application (default "smm-demo")
--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
--istio-revision string Istio control plane revision (format: [istio-resource-name].[namespace])
-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
19 - smm demoapp load start
smm demoapp load start
Start sending traffic to the demo application
Synopsis
The command starts a new deployment that will generate HTTP load on the demo application.
The generated load will vary over time, it will fluctuate between min-rps and max-rps over the
swing-period timeframe.
When invoked without additional flags the command will start loading the demo application with
sane defaults.
smm demoapp load start [flags]
Options
-h, --help help for start
--max-rps int Maximum RPS of the load (default 30)
--min-rps int Minimum RPS of the load (default 10)
--requests-cpu uint The load generator's requested cpu shares in millicores (default 250)
--requests-memory uint The load generator's requested memory in megabytes (default 128)
--rps int If specified a constant load of this RPS is put on the demo application
--swing-period duration How much time should it take to go from min to max and min again (default 23m0s)
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
--demo-namespace string Namespace for demo application (default "smm-demo")
--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
--istio-revision string Istio control plane revision (format: [istio-resource-name].[namespace])
-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
20 - smm demoapp load stop
smm demoapp load stop
Stop sending traffic to the demo application
Synopsis
The command destroys the deployment responsible for generating HTTP load on the demo application.
smm demoapp load stop [flags]
Options
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
--demo-namespace string Namespace for demo application (default "smm-demo")
--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
--istio-revision string Istio control plane revision (format: [istio-resource-name].[namespace])
-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
21 - smm demoapp uninstall
smm demoapp uninstall
Output or delete Kubernetes resources to uninstall demo application
Synopsis
Output or delete Kubernetes resources to uninstall demo application.
The command automatically removes the resources.
It can only dump the removable resources with the ‘–dump-resources’ option.
smm demoapp uninstall [flags]
Examples
# Default uninstall.
smm demoapp uninstall
# Uninstall demo application from a non-default namespace.
smm demoapp uninstall install -n custom-demoapp-ns
Options
-d, --dump-resources Dump resources to stdout instead of applying them
-h, --help help for uninstall
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
--demo-namespace string Namespace for demo application (default "smm-demo")
--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
--istio-revision string Istio control plane revision (format: [istio-resource-name].[namespace])
-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
22 - smm graph
smm graph
Show graph
smm graph [[--service=]namespace/servicename] [flags]
Options
-h, --help help for graph
--outbound Whether to show outbound or inbound metrics
-r, --refresh-interval duration the interval to refresh the dashboard (default 10s)
-d, --relative-duration duration the relative duration from now to load the graph (default 15m0s)
--title-suffix string Title suffix
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
23 - smm install
smm install
Install Service Mesh Manager
Synopsis
Installs Service Mesh Manager.
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.
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 (requires at least 3 nodes in the destination cluster)
-h, --help help for install
--install-cert-manager Whether to install cert manager (default true)
-a, --install-everything Install all required components at once
--istio-cr-file string Filename of a custom Istio CR yaml
--istio-namespace string Namespace of Istio sidecar injector (default "istio-system")
--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
24 - smm istio
smm istio
Install and manage Istio
Options
-h, --help help for istio
-n, --namespace string Namespace in which Istio is installed [$ISTIO_NAMESPACE] (default "istio-system")
-r, --revision string Control plane revision
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
25 - smm istio cluster
smm istio cluster
Manage Istio mesh member clusters
Options
-h, --help help for cluster
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)
-n, --namespace string Namespace in which Istio is installed [$ISTIO_NAMESPACE] (default "istio-system")
--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)
-r, --revision string Control plane revision
--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
26 - smm istio cluster attach
smm istio cluster attach
Attach peer cluster to the mesh
smm istio cluster attach [path-to-kubeconfig] [flags]
Options
--active-istio-control-plane Whether to deploy an active istio control plane to the attached cluster
--force Try to attach the cluster even if it is already attached
-h, --help help for attach
--name string Name override for the peer cluster
--network-name string Network name for the peer cluster
--peer-api-server-endpoint-address string The publicly accessible address of the peer cluster's k8s api server
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)
-n, --namespace string Namespace in which Istio is installed [$ISTIO_NAMESPACE] (default "istio-system")
--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)
-r, --revision string Control plane revision
--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
27 - smm istio cluster detach
smm istio cluster detach
Detach peer cluster from the mesh
smm istio cluster detach [kubeconfig] [flags]
Options
-h, --help help for detach
--name string Name override for the peer cluster
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)
-n, --namespace string Namespace in which Istio is installed [$ISTIO_NAMESPACE] (default "istio-system")
--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)
-r, --revision string Control plane revision
--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
28 - smm istio cluster status
smm istio cluster status
Show cluster status
smm istio cluster status [flags]
Options
-h, --help help for status
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)
-n, --namespace string Namespace in which Istio is installed [$ISTIO_NAMESPACE] (default "istio-system")
--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)
-r, --revision string Control plane revision
--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
29 - smm istio install
smm istio install
Installs Istio utilizing Banzai Cloud’s Istio-operator
Synopsis
Installs Istio utilizing Banzai Cloud’s Istio-operator.
The command automatically applies the resources.
It can only dump the applicable resources with the ‘–dump-resources’ option.
The manual mode is a two phase process as the operator needs custom CRDs to work.
The installer automatically detects whether the CRDs are installed or not, and behaves accordingly.
smm istio install [flags]
Examples
# Default install.
smm istio install
# Install Istio into a non-default namespace.
smm istio install -n istio-custom-ns
Options
--cluster-name string Name of the cluster
-d, --dump-resources Dump resources to stdout instead of applying them
--force Force Istio upgrade (only applicable in non-interactive mode)
-h, --help help for install
-f, --istio-cr-file string Filename of a custom Istio CR yaml
--release-name string Name of the release (default "istio-operator")
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)
-n, --namespace string Namespace in which Istio is installed [$ISTIO_NAMESPACE] (default "istio-system")
--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)
-r, --revision string Control plane revision
--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
30 - smm istio outbound-traffic-policy
smm istio outbound-traffic-policy
Set outbound traffic policy
smm istio outbound-traffic-policy [allowed|restricted] [flags]
Options
-h, --help help for outbound-traffic-policy
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)
-n, --namespace string Namespace in which Istio is installed [$ISTIO_NAMESPACE] (default "istio-system")
--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)
-r, --revision string Control plane revision
--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
31 - smm istio overview
smm istio overview
Show basic mesh overview metrics
smm istio overview [flags]
Options
-s, --evaluation-duration-seconds uint Metrics timespan in seconds (default 60)
-h, --help help for overview
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)
-n, --namespace string Namespace in which Istio is installed [$ISTIO_NAMESPACE] (default "istio-system")
--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)
-r, --revision string Control plane revision
--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
32 - smm istio uninstall
smm istio uninstall
Output or delete Kubernetes resources to uninstall Istio
Synopsis
Output or delete Kubernetes resources to uninstall Istio.
The command automatically removes the resources.
It can only dump the removable resources with the ‘–dump-resources’ option.
smm istio uninstall [flags]
Examples
# Default uninstall.
smm istio uninstall
# Uninstall Istio from a non-default namespace.
smm istio uninstall -n custom-istio-ns
Options
-d, --dump-resources Dump resources to stdout instead of applying them
-h, --help help for uninstall
--release-name string Name of the release (default "istio-operator")
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)
-n, --namespace string Namespace in which Istio is installed [$ISTIO_NAMESPACE] (default "istio-system")
--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)
-r, --revision string Control plane revision
--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
33 - smm license
smm license
Manage license
Options
-h, --help help for license
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
34 - smm license apply
smm license apply
Apply SMM license
smm license apply [flags]
Options
-h, --help help for apply
--licenseKeyPath string Path to SMM license key
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
35 - smm license list
smm license list
List SMM license
Options
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
36 - smm license remove
smm license remove
Remove SMM license
smm license remove [flags]
Options
-h, --help help for remove
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
37 - smm login
smm login
Log in to Service Mesh Manager
Options
-h, --help help for login
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
38 - smm operator
smm operator
Install and manage Service Mesh Manager operator
Options
-h, --help help for operator
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
39 - smm operator reconcile
smm operator reconcile
smm operator reconcile [flags]
Options
-h, --help help for reconcile
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 operator - Install and manage Service Mesh Manager operator
40 - smm registry
smm registry
Manage private registry access for Service Mesh Manager
Options
-h, --help help for registry
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
- smm registry add - Add new docker private registry using basic authentication to the SMM deployment.
- smm registry ecr - Add new ECR based registry to the Service Mesh Manager deployment.
- smm registry list - Display private registry settings for Service Mesh Manager deployments.
- smm registry override - override default image location for Service Mesh Manager images
- smm registry reconcile - Update the remote cluster’s image pull secrets from the local settings.
- smm registry remove - Remove a registry from the list of registries used by Service Mesh Manager for image pulling.
41 - smm registry add
smm registry add
Add new docker private registry using basic authentication to the SMM deployment.
Synopsis
Add new docker private registry using basic authentication to the SMM deployment.
If the password argument is not specified, the CLI will ask the password interactively.
To add a dockerhub user please specify https://index.docker.io/v1/ as URL.
Note: the changes are only saved locally, to update the remote cluster please call:
smm registry reconcile
smm registry add [flags] registryUrl registryUserName [password]
Options
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 registry - Manage private registry access for Service Mesh Manager
42 - smm registry ecr
smm registry ecr
Add new ECR based registry to the Service Mesh Manager deployment.
Synopsis
Add new ECR based registry to the Service Mesh Manager deployment.
If the password argument is not specified, the CLI will ask the password interactively.
Note: the changes are only saved locally, to update the remote cluster please call:
smm registry reconcile
smm registry ecr [flags] account-id region access-key-id [secret-access-key]
Options
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 registry - Manage private registry access for Service Mesh Manager
43 - smm registry list
smm registry list
Display private registry settings for Service Mesh Manager deployments.
smm registry list [flags]
Options
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 registry - Manage private registry access for Service Mesh Manager
44 - smm registry override
smm registry override
override default image location for Service Mesh Manager images
Options
-h, --help help for override
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
45 - smm registry override reset
smm registry override reset
disable image overrides for Service Mesh Manager images
Synopsis
disable image overrides for Service Mesh Manager images
smm registry override reset [flags]
Options
-h, --help help for reset
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
46 - smm registry override set
smm registry override set
override default image location for Service Mesh Manager images
Synopsis
override default image location for Service Mesh Manager images
Image names, if override is set, will be constructed the following way:
<host>/<prefix>/<image>:<tag>
For example, in case of the Service Mesh Manager API server whose name is (<image>
) smm, and the
<host>
is set to myrepo.example.org, while <prefix>
is set to smm-mirror the images will be
downloaded:
myrepo.example.org/smm-mirror/smm:<tag>
smm registry override set [flags]
Options
-h, --help help for set
--host string Host name of the docker registry server to fetch Service Mesh Manager images
--prefix string URL prefix the docker repository to fetch Service Mesh Manager images
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
47 - smm registry override status
smm registry override status
show image override status for Service Mesh Manager images
Synopsis
show image override status for Service Mesh Manager images
smm registry override status [flags]
Options
-h, --help help for status
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
48 - smm registry reconcile
smm registry reconcile
Update the remote cluster’s image pull secrets from the local settings.
Synopsis
Update the remote cluster’s image pull secrets from the local settings.
The command will update the ControlPlane CR and execute a reconciliation so that the pull secrets configuration is
updated in the cluster.
smm registry reconcile [flags]
Options
-h, --help help for reconcile
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 registry - Manage private registry access for Service Mesh Manager
49 - smm registry remove
smm registry remove
Remove a registry from the list of registries used by Service Mesh Manager for image pulling.
Synopsis
Remove a registry from the list of registries used by Service Mesh Manager for image pulling.
Note: the changes are only saved locally, to update the remote cluster please call:
smm registry reconcile
smm registry remove [flags] registryUrl
Options
-h, --help help for remove
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 registry - Manage private registry access for Service Mesh Manager
50 - smm sdm
Manage Streaming Data Manager.
51 - smm sdm cluster
Manage Kafka clusters on a Kubernetes cluster.
Synopsis
Manage Kafka clusters on a Kubernetes cluster.
Options
-h, --help help for cluster
Options inherited from parent commands
--color use colors on non-tty outputs (default true)
--context string name of the kubeconfig context to use
--formatting.force-color force color even when non in a terminal
--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
--non-interactive never ask questions interactively
-o, --output string output format (table|yaml|json) (default "table")
--persistent-config-file string Streaming Data Manager persistent config file to use instead of the default at ~/.banzai/supertubes/
-v, --verbose turn on debug logging
52 - smm sdm cluster kafka-connect
Manage Kafka Connect deployments
Synopsis
Manage Kafka Connect deployments
Options
-h, --help help for kafka-connect
Options inherited from parent commands
--color use colors on non-tty outputs (default true)
--context string name of the kubeconfig context to use
--formatting.force-color force color even when non in a terminal
--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
--non-interactive never ask questions interactively
-o, --output string output format (table|yaml|json) (default "table")
--persistent-config-file string Streaming Data Manager persistent config file to use instead of the default at ~/.banzai/supertubes/
-v, --verbose turn on debug logging
SEE ALSO
- [smm sdm cluster](/docs/reference/cli/reference/smm_sdm_cluster/ - Manage Kafka clusters on a Kubernetes cluster.
- [smm sdm cluster kafka-connect create](/docs/reference/cli/reference/smm_sdm_cluster_kafka-connect_create/ - Create Kafka Connect instance.
- [smm sdm cluster kafka-connect delete](/docs/reference/cli/reference/smm_sdm_cluster_kafka-connect_delete/ - Deletes Kafka Connect instance.
- [smm sdm cluster kafka-connect get](/docs/reference/cli/reference/smm_sdm_cluster_kafka-connect_get/ - Gets Kafka Connect details.
- [smm sdm cluster kafka-connect update](/docs/reference/cli/reference/smm_sdm_cluster_kafka-connect_update/ - Update a Kafka Connect instance
53 - smm sdm cluster kafka-connect create
Create Kafka Connect instance.
Synopsis
Create Kafka Connect instance based on json/yaml stdin or file config
smm sdm cluster kafka-connect create [flags]
Examples
# Create Kafka Connect instance from config file
$ smm sdm cluster kafka-connect create -f <path-to-kafka-connect-config-file> -n my-namespace -c <path-to-kubeconfig-file>
# Create Kafka Connect from config file and wait to become active
$ smm sdm cluster kafka-connect create -f <path-to-kafka-connect-config-file> -n my-namespace -c <path-to-kubeconfig-file> -w
# Create Kafka Connect from stdin and wait to become active
$ cat <path-to-kafka-connect-config-file> | smm sdm cluster kafka-connect create -n my-namespace -c <path-to-kubeconfig-file> -w
Options
-f, --config-file string Config file that contains the Kafka Connect config.
--create-service-account Whether to create the service accounts specified in the Kafka Connect descriptor. If this option is set to 'true' and there are no service accounts specified in the Kafka Connect descriptor than a service account with <kafka-connect-name>-kafka-connect will be created. (default true)
-h, --help help for create
-i, --interval int Interval in seconds for polling Kafka Connect status. (default 5)
-k, --kafka-cluster string Name of the Kafka cluster which this Kafka Connect instance will connect to. (default "kafka")
-n, --namespace string Namespace that will host the Kafka Connect instance. (default "kafka")
-r, --schema-registry string Name of the Schema Registry which this Kafka Connect instance will use for schemas.
-t, --timeout int Timeout in seconds to wait for the Kafka Connect create operation to complete. (default 150)
-w, --wait Wait for Kafka Connect create operation to complete.
Options inherited from parent commands
--color use colors on non-tty outputs (default true)
--context string name of the kubeconfig context to use
--formatting.force-color force color even when non in a terminal
--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
--non-interactive never ask questions interactively
-o, --output string output format (table|yaml|json) (default "table")
--persistent-config-file string Streaming Data Manager persistent config file to use instead of the default at ~/.banzai/supertubes/
-v, --verbose turn on debug logging
SEE ALSO
- [smm sdm cluster kafka-connect](/docs/reference/cli/reference/smm_sdm_cluster_kafka-connect/ - Manage Kafka Connect deployments
54 - smm sdm cluster kafka-connect delete
Deletes Kafka Connect instance.
Synopsis
Deletes Kafka Connect instance.
smm sdm cluster kafka-connect delete [--kafka-connect=]NAME [flags]
Examples
# Delete the selected Kafka Connect instance
$ smm sdm cluster kafka-connect delete
# Delete the my-kafka-connect Kafka Connect from namespace my-namespace
$ smm sdm cluster kafka-connect delete my-kafka-connect -n my-namespace -c <path-to-kubeconfig-file>
# Delete the my-kafka-connect Kafka Connect from namespace my-namespace and wait for the completion of the deletion
$ smm sdm cluster kafka-connect delete my-kafka-connect -n my-namespace -c <path-to-kubeconfig-file> -w
Options
-h, --help help for delete
-i, --interval int Interval in seconds for polling Kafka Connect status. (default 5)
--kafka-connect string Name of the Kafka Connect instance to be deleted.
-n, --namespace string Namespace to delete the Kafka Connect instance from. (default "kafka")
-t, --timeout int Timeout in seconds to wait for the Kafka Connect delete operation to complete. (default 120)
-w, --wait Wait for Kafka Connect delete operation to complete.
Options inherited from parent commands
--color use colors on non-tty outputs (default true)
--context string name of the kubeconfig context to use
--formatting.force-color force color even when non in a terminal
--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
--non-interactive never ask questions interactively
-o, --output string output format (table|yaml|json) (default "table")
--persistent-config-file string Streaming Data Manager persistent config file to use instead of the default at ~/.banzai/supertubes/
-v, --verbose turn on debug logging
SEE ALSO
- [smm sdm cluster kafka-connect](/docs/reference/cli/reference/smm_sdm_cluster_kafka-connect/ - Manage Kafka Connect deployments
55 - smm sdm cluster kafka-connect get
Gets Kafka Connect details.
Synopsis
Gets Kafka Connect details.
smm sdm cluster kafka-connect get [--kafka-connect=]NAME [flags]
Examples
# Get the details of the selected Kafka Connect instance
$ smm sdm cluster kafka-connect get
# Get the details of the my-kafka-connect Kafka Connect from namespace my-namespace
$ smm sdm cluster kafka-connect get my-kafka-connect -n my-namespace -c <path-to-kubeconfig-file>
# Get the details of the my-kafka-connect Kafka Connect from namespace my-namespace in yaml format
$ smm sdm cluster kafka-connect get my-kafka-connect -n my-namespace -c <path-to-kubeconfig-file> -o yaml
Options
-h, --help help for get
--kafka-connect string Name of the Kafka Connect instance to retrieve.
-n, --namespace string Namespace where to lookup the Kafka Connect instance. (default "kafka")
Options inherited from parent commands
--color use colors on non-tty outputs (default true)
--context string name of the kubeconfig context to use
--formatting.force-color force color even when non in a terminal
--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
--non-interactive never ask questions interactively
-o, --output string output format (table|yaml|json) (default "table")
--persistent-config-file string Streaming Data Manager persistent config file to use instead of the default at ~/.banzai/supertubes/
-v, --verbose turn on debug logging
SEE ALSO
- [smm sdm cluster kafka-connect](/docs/reference/cli/reference/smm_sdm_cluster_kafka-connect/ - Manage Kafka Connect deployments
56 - smm sdm cluster kafka-connect update
Update a Kafka Connect instance
Synopsis
Update a Kafka Connect instance based on JSON or YAML stdin or file config
smm sdm cluster kafka-connect update [flags]
Examples
# Update Kafka Connect from config file
$ smm sdm cluster kafka-connect update -f <path-to-kafka-connect-config-file> -n my-namespace --kafka-connect my-kafka-connect -c <path-to-kubeconfig-file>
# Update Kafka Connect from config file and wait for the updated Kafka Connect instance to be restarted
$ smm sdm cluster kafka-connect update -f <path-to-kafka-connect-config-file> -n my-namespace --kafka-connect my-kafka-connect -c <path-to-kubeconfig-file> -w
# Update only the Kafka Connect image of the deployment and wait for the Kafka Connect instance to be restarted
$ smm sdm cluster kafka-connect update -n my-namespace --kafka-connect my-kafka-connect --kafka-connect-image "confluentinc/cp-kafka-connect:6.0.0" -c <path-to-kubeconfig-file> -w
# Patch Kafka Connect config
$ smm sdm cluster kafka-connect update -n my-namespace --kafka-connect my-kafka-connect -c <path-to-kubeconfig-file> -w -f -<<EOF
apiVersion: kafka.banzaicloud.io/v1beta1
kind: KafkaConnect
spec:
MTLS: true
EOF
Options
-f, --config-file string Config file that contains the Kafka Connect config.
-h, --help help for update
-i, --interval int Interval in seconds for polling Kafka Connect status. (default 5)
--kafka-connect string Name of the Kafka Connect instance to be updated.
--kafka-connect-image string The new image (repository/name:tag) to update Kafka Connect to.
-n, --namespace string Namespace the Kafka Connect instance to be updated belongs to. (default "kafka")
-t, --timeout int Timeout in seconds to wait for the Kafka Connect update operation to complete. (default 150)
-w, --wait Wait for Kafka Connect update operation to complete.
Options inherited from parent commands
--color use colors on non-tty outputs (default true)
--context string name of the kubeconfig context to use
--formatting.force-color force color even when non in a terminal
--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
--non-interactive never ask questions interactively
-o, --output string output format (table|yaml|json) (default "table")
--persistent-config-file string Streaming Data Manager persistent config file to use instead of the default at ~/.banzai/supertubes/
-v, --verbose turn on debug logging
SEE ALSO
- [smm sdm cluster kafka-connect](/docs/reference/cli/reference/smm_sdm_cluster_kafka-connect/ - Manage Kafka Connect deployments
57 - smm sdm cluster kafka-connector
Manage Kafka Connectors
Synopsis
Manage Kafka Connectors
Options
-h, --help help for kafka-connector
Options inherited from parent commands
--color use colors on non-tty outputs (default true)
--context string name of the kubeconfig context to use
--formatting.force-color force color even when non in a terminal
--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
--non-interactive never ask questions interactively
-o, --output string output format (table|yaml|json) (default "table")
--persistent-config-file string Streaming Data Manager persistent config file to use instead of the default at ~/.banzai/supertubes/
-v, --verbose turn on debug logging
SEE ALSO
- [smm sdm cluster](/docs/reference/cli/reference/smm_sdm_cluster/ - Manage Kafka clusters on a Kubernetes cluster.
- [smm sdm cluster kafka-connector create](/docs/reference/cli/reference/smm_sdm_cluster_kafka-connector_create/ - Create Kafka Connector instance.
- [smm sdm cluster kafka-connector delete](/docs/reference/cli/reference/smm_sdm_cluster_kafka-connector_delete/ - Deletes Kafka Connector instance.
- [smm sdm cluster kafka-connector get](/docs/reference/cli/reference/smm_sdm_cluster_kafka-connector_get/ - Gets Kafka Connector details.
- [smm sdm cluster kafka-connector update](/docs/reference/cli/reference/smm_sdm_cluster_kafka-connector_update/ - Update a Kafka Connector instance
58 - smm sdm cluster kafka-connector
Manage Streaming Data Manager.
59 - smm sdm cluster kafka-connector
Update a Kafka Connector instance
Synopsis
Update a Kafka Connector instance based on JSON or YAML stdin or file config
smm sdm cluster kafka-connector update [flags]
Examples
# Update Kafka Connector from config file
$ smm sdm cluster kafka-connector update -f <path-to-kafka-connector-config-file> -n my-namespace --kafka-connector my-kafka-connector -c <path-to-kubeconfig-file>
# Patch Kafka Connector config
$ smm sdm cluster kafka-connector update -n my-namespace --kafka-connector my-kafka-connector -c <path-to-kubeconfig-file> -w -f -<<EOF
apiVersion: kafka.banzaicloud.io/v1beta1
kind: KafkaConnector
spec:
pause: true
EOF
Options
-f, --config-file string Config file that contains the Kafka Connector config.
-h, --help help for update
--kafka-connect string Name of the Kafka Connector instance to be updated.
-n, --namespace string Namespace the Kafka Connector instance to be updated belongs to. (default "kafka")
Options inherited from parent commands
--color use colors on non-tty outputs (default true)
--context string name of the kubeconfig context to use
--formatting.force-color force color even when non in a terminal
--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
--non-interactive never ask questions interactively
-o, --output string output format (table|yaml|json) (default "table")
--persistent-config-file string Streaming Data Manager persistent config file to use instead of the default at ~/.banzai/supertubes/
-v, --verbose turn on debug logging
SEE ALSO
- [smm sdm cluster kafka-connector](/docs/reference/cli/reference/smm_sdm_cluster_kafka-connector/ - Manage Kafka Connectors
60 - smm sdm cluster kafka-connector delete
Deletes Kafka Connector instance.
Synopsis
Deletes Kafka Connector instance.
smm sdm cluster kafka-connector delete [--kafka-connector=]NAME [flags]
Examples
# Delete the selected Kafka Connector instance
$ smm sdm cluster kafka-connector delete
# Delete the my-kafka-connector Kafka Connector from namespace my-namespace
$ smm sdm cluster kafka-connector delete my-kafka-connector -n my-namespace -c <path-to-kubeconfig-file>
# Delete the my-kafka-connector Kafka Connector from namespace my-namespace and wait for the completion of the deletion
$ smm sdm cluster kafka-connector delete my-kafka-connector -n my-namespace -c <path-to-kubeconfig-file> -w
Options
-h, --help help for delete
-i, --interval int Interval in seconds for polling Kafka Connector status. (default 5)
--kafka-connector string Name of the Kafka Connector instance to be deleted.
-n, --namespace string Namespace to delete the Kafka Connector instance from. (default "kafka")
-t, --timeout int Timeout in seconds to wait for the Kafka Connector delete operation to complete. (default 120)
-w, --wait Wait for Kafka Connector delete operation to complete.
Options inherited from parent commands
--color use colors on non-tty outputs (default true)
--context string name of the kubeconfig context to use
--formatting.force-color force color even when non in a terminal
--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
--non-interactive never ask questions interactively
-o, --output string output format (table|yaml|json) (default "table")
--persistent-config-file string Streaming Data Manager persistent config file to use instead of the default at ~/.banzai/supertubes/
-v, --verbose turn on debug logging
SEE ALSO
- [smm sdm cluster kafka-connector](/docs/reference/cli/reference/smm_sdm_cluster_kafka-connector/ - Manage Kafka Connectors
61 - smm sdm cluster kafka-connector get
Gets Kafka Connector details.
Synopsis
Gets Kafka Connector details.
smm sdm cluster kafka-connector get [--kafka-connector=]NAME [flags]
Examples
# Get the details of the selected Kafka Connector instance
$ smm sdm cluster kafka-connector get
# Get the details of the my-kafka-connector Kafka Connector from namespace my-namespace
$ smm sdm cluster kafka-connector get my-kafka-connector -n my-namespace -c <path-to-kubeconfig-file>
# Get the details of the my-kafka-connector Kafka Connector from namespace my-namespace in yaml format
$ smm sdm cluster kafka-connector get my-kafka-connector -n my-namespace -c <path-to-kubeconfig-file> -o yaml
Options
-h, --help help for get
--kafka-connector string Name of the Kafka Connector instance to retrieve.
-n, --namespace string Namespace where to lookup the Kafka Connector instance. (default "kafka")
Options inherited from parent commands
--color use colors on non-tty outputs (default true)
--context string name of the kubeconfig context to use
--formatting.force-color force color even when non in a terminal
--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
--non-interactive never ask questions interactively
-o, --output string output format (table|yaml|json) (default "table")
--persistent-config-file string Streaming Data Manager persistent config file to use instead of the default at ~/.banzai/supertubes/
-v, --verbose turn on debug logging
SEE ALSO
- [smm sdm cluster kafka-connector](/docs/reference/cli/reference/smm_sdm_cluster_kafka-connector/ - Manage Kafka Connectors
62 - smm sdm cluster update
Manage Streaming Data Manager.
63 - smm sdm mirror-maker2
Manage Streaming Data Manager installation.
64 - smm sdm prometheus
Manage Streaming Data Manager installation.
65 - smm sdm zookeeper
Manage Streaming Data Manager installation.
66 - smm sidecar-proxy
smm sidecar-proxy
Manage sidecar-proxy related configurations
Options
-h, --help help for sidecar-proxy
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
67 - smm sidecar-proxy auto-inject
smm sidecar-proxy auto-inject
Manage auto-injection configurations
Options
-h, --help help for auto-inject
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
68 - smm sidecar-proxy auto-inject off
smm sidecar-proxy auto-inject off
Disable sidecar injection for the given namespace
smm sidecar-proxy auto-inject off [[--namespace=]name] [flags]
Options
-h, --help help for off
--namespace string Namespace name
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
69 - smm sidecar-proxy auto-inject on
smm sidecar-proxy auto-inject on
Enable sidecar injection for the given namespace
smm sidecar-proxy auto-inject on [[--namespace=]name] [flags]
Options
-h, --help help for on
--namespace string Namespace name
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
70 - smm sidecar-proxy egress
smm sidecar-proxy egress
Manage sidecar egress configurations
Options
-h, --help help for egress
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
71 - smm sidecar-proxy egress recommend
smm sidecar-proxy egress recommend
Recommend sidecar configuration for a workload
smm sidecar-proxy egress recommend [--namespace] namespace [--workload name] [--isolationLevel=NAMESPACE|WORKLOAD] [--labelWhitelist=label] [flags]
Options
--apply Apply recommendations
-h, --help help for recommend
-i, --isolationLevel string Isolation level (NAMESPACE|WORKLOAD)
-l, --labelWhitelist stringArray Labels to include in the workload selector
--namespace string Namespace name
--workload string Workload name
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
72 - smm tap
smm tap
Tap into HTTP/GRPC mesh traffic
smm tap [[ns|workload|pod]/resource-name] [flags]
Examples
# tap the movies-v1 deployment in the default namespace
smm tap workload/movies-v1
# tap the movies-v1-7f9645bfd7-8vgm9 pod in the default namespace
smm tap pod/movies-v1-7f9645bfd7-8vgm9
# tap the smm-demo namespace
smm tap ns/smm-demo
# tap the smm-demo namespace request to test namespace
smm tap ns/smm-demo --destination ns/test
Options
--authority string Show requests with this authority
--destination string Show requests to this resource
--destination-ns string Namespace of the destination resource; by default the current "--namespace" is used
--direction string Show requests with this direction (inbound|outbound)
-h, --help help for tap
--max-rps uint Limits maximum requests per second from the logstream
--method string Show requests with this request method
--ns string Namespace of the specified resource (default "default")
--path string Show requests with paths with this prefix
--request-header strings Filter for request header (name:value).
Filters for existence of the header if only the name is specified, otherwise uses case-sensitive prefix match for the value.
--response-code uints Show request with this response code (default [])
--response-header strings Filter for response header (name:value).
Filters for existence of the header if only the name is specified, otherwise uses case-sensitive prefix match for the value.
--scheme string Show requests with this scheme
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
73 - smm uninstall
smm uninstall
Uninstall Service Mesh Manager
Synopsis
Uninstall Service Mesh Manager
The command automatically removes the resources.
It can only dump the removable resources with the ‘–dump-resources’ option.
Examples
# Default uninstall
smm uninstall
# Uninstall Service Mesh Manager from a non-default namespace
smm uninstall -n smm-system
Options
-d, --dump-resources Dump resources to stdout instead of applying them
--force-uninstall Do not prompt for confirmation
-h, --help help for uninstall
--istio-namespace string Namespace of Istio sidecar injector (default "istio-system")
--release-name string Name of the release (default "smm")
-a, --uninstall-everything Uninstall all components at once
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
74 - smm version
smm version
Print the client and api version information
Options
--client Print the client version only
-h, --help help for version
--short Print the version number(s) only, with no additional output
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