telepresence setup

Analyze the cluster and propose or apply a traffic-manager configuration

Synopsis:

Analyze the cluster and propose or apply a traffic-manager configuration.

The command probes the cluster (privileges, QUIC and node-agent viability, webhook creation, namespace scale, and any existing installation), then asks only the questions the findings leave open, including whether to enforce caller authentication, the required grant, an external control endpoint, and legacy client access, and prints a report with the values. At least one of --output and --apply is required: --output writes the values file (--output - for a read-only run that only prints them), and --apply installs or upgrades the traffic-manager; passing both writes the file and applies it.

Usage:

  telepresence setup [flags]

Flags:

      --apply                      Install/upgrade the traffic-manager with the resulting values
  -h, --help                       help for setup
      --input string               Read a Helm values file; its settings become pinned defaults
      --manager-namespace string   The namespace where the traffic manager is to be found. Overrides any other manager namespace set in config
      --non-interactive            Never prompt; unanswered questions fall back to input-pinned settings or safe defaults
      --output string              Write the resulting Helm values to this file, suitable for a Helm install; "-" writes them to stdout and suppresses the report

Kubernetes flags:

      --as string                      Username to impersonate for the operation. User could be a regular user or a service account in a namespace.
      --as-group stringArray           Group to impersonate for the operation, this flag can be repeated to specify multiple groups.
      --as-uid string                  UID to impersonate for the operation.
      --as-user-extra stringArray      User extras to impersonate for the operation, this flag can be repeated to specify multiple values for the same key.
      --cache-dir string               Default cache directory (default "$HOME/.kube/cache")
      --certificate-authority string   Path to a cert file for the certificate authority
      --client-certificate string      Path to a client certificate file for TLS
      --client-key string              Path to a client key file for TLS
      --cluster string                 The name of the kubeconfig cluster to use
      --context string                 The name of the kubeconfig context to use
      --disable-compression            If true, opt-out of response compression for all requests to the server
      --insecure-skip-tls-verify       If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure
      --kubeconfig string              Path to the kubeconfig file to use for CLI requests.
      --proxy-url string               Proxy URL to use for requests to the API server
      --request-timeout string         The length of time to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't timeout requests. (default "0")
  -s, --server string                  The address and port of the Kubernetes API server
      --tls-server-name string         Server name to use for server certificate validation. If it is not provided, the hostname used to contact the server is used
      --token string                   Bearer token for authentication to the API server
      --user string                    The name of the kubeconfig user to use

Global Flags:

      --config string     Path to the Telepresence configuration file
      --format string     Set the output format, supported values are 'json', 'yaml', 'json-stream', and 'default' (default "default")
      --progress string   Set type of progress output (auto, tty, plain, json, quiet) (default "auto")
      --use string        Match expression that uniquely identifies the daemon container