istioctl gen-deploy --help

istio-gen-deploy.bash

ceposta@postamacpro(~) $ istioctl gen-deploy --help
istioctl gen-deploy produces deployment files to run the minimum Istio control for the set of features requested by the --feature flag. If no features are provided, we create deployments for the default control plane: Pilot, Mixer, CA, and Ingress Proxies, with mTLS enabled.

Usage:
  istioctl gen-deploy [flags]

Examples:
istioctl gen-deploy --features routing,policy,initializer -o helm

Flags:
      --debug                      If true, uses debug images instead of release images
  -f, --features stringArray       List of Istio features to enable. Accepts any combination of "mtls", "telemetry", "routing", "ingress", "policy", "initializer".
      --helm-chart-dir string      The directory to find the helm charts used to render Istio deployments. -o yaml uses these to render the helm chart locally. (default ".")
  -h, --help                       help for gen-deploy
      --hyperkube-hub string       The container registry to pull Hyperkube images from (default "quay.io/coreos/hyperkube")
      --hyperkube-tag Hyperkube    The tag to use to pull the Hyperkube container (default "0.4.0")
      --ingress-node-port uint16   If provided, Istio ingress proxies will run as a NodePort service mapped to the port provided by this flag. Note that this flag is ignored unless the "ingress" feature flag is provided too.
  -o, --out string                 Output format. Acceptable values are:
					"helm": produces contents of values.yaml
					"yaml": produces Kubernetes deployments (default "helm")
      --values string              Path to the Helm values.yaml file used to render YAML deployments locally when --out=yaml. Flag values are ignored in favor of using the file directly.

Global Flags:
  -i, --istioNamespace string            Istio system namespace (default "istio-system")
  -c, --kubeconfig string                Kubernetes configuration file (default "/Users/ceposta/.kube/config")
      --log_as_json                      Whether to format output as JSON or in plain console-friendly format
      --log_backtrace_at traceLocation   when logging hits line file:N, emit a stack trace (default :0)
      --log_callers                      Include caller information, useful for debugging
      --log_output_level string          The minimum logging level of messages to output, can be one of "debug", "info", "warn", "error", or "none" (default "info")
      --log_rotate string                The path for the optional rotating log file
      --log_rotate_max_age int           The maximum age in days of a log file beyond which the file is rotated (0 indicates no limit) (default 30)
      --log_rotate_max_backups int       The maximum number of log file backups to keep before older files are deleted (0 indicates no limit) (default 1000)
      --log_rotate_max_size int          The maximum size in megabytes of a log file beyond which the file is rotated (default 104857600)
      --log_stacktrace_level string      The minimum logging level at which stack traces are captured, can be one of "debug", "info", "warn", "error", or "none" (default "none")
      --log_target stringArray           The set of paths where to output the log. This can be any path as well as the special values stdout and stderr (default [stdout])
  -n, --namespace string                 Config namespace
  -p, --platform string                  Istio host platform (default "kube")
  -v, --v Level                          log level for V logs
      --vmodule moduleSpec               comma-separated list of pattern=N settings for file-filtered logging