fleet deploy

Deploy a bundledeployment/content resource to a cluster, by creating a Helm release. This will not deploy the bundledeployment/content resources directly to the cluster.

  1. fleet deploy [flags]

Options

  1.   -a, --agent-namespace string            Set the agent namespace, normally cattle-fleet-system. If set, fleet agent will garbage collect the helm release, i.e. delete it if the bundledeployment is missing.
  2.   -d, --dry-run                           Print the resources that would be deployed, but do not actually deploy them
  3.   -h, --help                              help for deploy
  4.   -i, --input-file string                 Location of the YAML file containing the content and the bundledeployment resource
  5.       --kubeconfig string                 Paths to a kubeconfig. Only required if out-of-cluster.
  6.   -n, --namespace string                  Set the default namespace. Deploy helm chart into this namespace.
  7.       --zap-devel                         Development Mode defaults(encoder=consoleEncoder,logLevel=Debug,stackTraceLevel=Warn). Production Mode defaults(encoder=jsonEncoder,logLevel=Info,stackTraceLevel=Error) (default true)
  8.       --zap-encoder encoder               Zap log encoding (one of 'json' or 'console')
  9.       --zap-log-level level               Zap Level to configure the verbosity of logging. Can be one of 'debug', 'info', 'error', or any integer value > 0 which corresponds to custom debug levels of increasing verbosity
  10.       --zap-stacktrace-level level        Zap Level at and above which stacktraces are captured (one of 'info', 'error', 'panic').
  11.       --zap-time-encoding time-encoding   Zap time encoding (one of 'epoch', 'millis', 'nano', 'iso8601', 'rfc3339' or 'rfc3339nano'). Defaults to 'epoch'.

SEE ALSO